VulnerabilityPublished 25 Jul 2025

CVE-2025-30086: harbor · Information Exposure

Affects harborSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium : upgrade to 2.13.1 or 2.12.4 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.13.1, 2.12.4

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade goharbor/harbor to 2.13.1 or 2.12.4.

Affected software

Product	Affected	Fixed in
GitHubgoharbor/harbor`pkg:github/goharbor/harbor`Other threats	Affected <2.12.4 <2.13.1	Fixed in 2.12.4 2.13.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade affected Harbor instances to versions 2.13.1 or 2.12.4 or later, where this vulnerability is patched. Until upgrades can be performed, organizations should restrict administrator access to Harbor to a minimal set of trusted personnel and enforce strong multi-factor authentication (MFA) to reduce the risk of credential compromise. Monitoring and auditing Harbor API usage, especially queries involving the q parameter, can help detect suspicious activity indicative of exploitation attempts. Network segmentation should be applied to isolate Harbor instances from less trusted network zones. Additionally, organizations should rotate Harbor user credentials and any associated secrets after patching to mitigate potential credential exposure. Implementing strict role-based access control (RBAC) policies within Harbor can limit the number of users with administrator privileges, reducing the attack surface. Finally, organizations should keep abreast of official Harbor security advisories and apply patches promptly to address any future related vulnerabilities.

Description

CNCF Harbor 2.13.x before 2.13.1 and 2.12.x before 2.12.4 allows information disclosure by administrators who can exploit an ORM Leak present in the /api/v2.0/users endpoint to leak users' password hash and salt values. The q URL parameter allows a user to filter users by any column, and filter password=~ could be abused to leak out a user's password hash character by character. An attacker with administrator access could exploit this to leak highly sensitive information stored in the Harbor database. All endpoints that support the q URL parameter are vulnerable to this ORM leak attack.

Impact

For European organizations, this vulnerability poses a significant risk to container image security and overall cloud-native infrastructure integrity. Harbor is widely adopted in Europe due to the region's strong emphasis on cloud-native technologies and container orchestration platforms like Kubernetes. An attacker exploiting this vulnerability can obtain password hashes and salts of Harbor users, potentially cracking them offline to gain unauthorized access. This can lead to unauthorized image uploads, downloads, or deletions, disrupting CI/CD pipelines, software supply chains, and production environments. The exposure of credential data also increases the risk of lateral movement within corporate networks, potentially affecting other critical systems. Given the GDPR and other stringent data protection regulations in Europe, any compromise involving user credentials and sensitive infrastructure data can result in severe compliance violations, financial penalties, and reputational damage. The requirement for administrator access limits the threat to insiders or attackers who have already breached perimeter defenses, but the severity remains high due to the sensitive nature of the leaked information and the critical role Harbor plays in container security.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jul 2025, 14:47 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats