CVE-2025-30086

Workarounds

NA

References

Credit

[email protected]

Administrator users on Harbor could exploit an ORM Leak (https://www.elttam.com/blog/plormbing-your-django-orm/) vulnerability that was present in the /api/v2.0/users endpoint to leak users' password hash and salt values. This vulnerability was introduced into the application because the q URL parameter allowed the administrator to filter users by any column, and the filter password=~ could be abused to leak out a user's password hash character by character.

An attacker with administrator access could exploit this vulnerability to leak highly sensitive information stored on the Harbor database, as demonstrated in the attached writeup by the leaking of users' password hashes and salts. All endpoints that support the q URL parameter are vulnerable to this ORM leak attack, and could potentially be exploitable by lower privileged users to gain unauthorised access to other sensitive information.

CVE-2025-30086 has a CVSS score of 4.9 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.13.1, 2.12.4, 2.4.0-rc1.0.20250331071157-dce7d9f5cffb); upgrading removes the vulnerable code path.

Kodem intelligence

No available

1. What is CVE-2025-30086? CVE-2025-30086 is a medium-severity security vulnerability in github.com/goharbor/harbor (go), affecting versions = 2.13.0. It is fixed in 2.13.1, 2.12.4, 2.4.0-rc1.0.20250331071157-dce7d9f5cffb.
2. How severe is CVE-2025-30086? CVE-2025-30086 has a CVSS score of 4.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/goharbor/harbor are affected by CVE-2025-30086? github.com/goharbor/harbor (go) versions = 2.13.0 is affected.
4. Is there a fix for CVE-2025-30086? Yes. CVE-2025-30086 is fixed in 2.13.1, 2.12.4, 2.4.0-rc1.0.20250331071157-dce7d9f5cffb. Upgrade to this version or later.
5. Is CVE-2025-30086 exploitable, and should I be worried? Whether CVE-2025-30086 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-30086 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-30086?
   • Upgrade github.com/goharbor/harbor to 2.13.1 or later
   • Upgrade github.com/goharbor/harbor to 2.12.4 or later
   • Upgrade github.com/goharbor/harbor to 2.4.0-rc1.0.20250331071157-dce7d9f5cffb or later