Skip to content
Fencer Intel
medium 4.9

CVE-2025-30086 json

Possible ORM Leak Vulnerability in the Harbor

published last yr. modified 4mo ago also GHSA-h27m-3qw8-3pw8 , GO-2025-3826 , EUVD-2025-22653

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/goharbor/harbor 2.4.0-rc1.0.20250331071157-dce7d9f5cffb, 2.12.4, 2.12.4+incompatible, 2.13.1, 2.13.1+incompatible
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1

opensuse advisories openSUSE-SU-2025:15405-1

Is CVE-2025-30086 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/goharbor/harbor
>=2.13.0, <2.13.1
>=2.4.0-rc1.1, <2.12.4
<2.4.0-rc1.0.20250331071157-dce7d9f5cffb
<2.12.4+incompatible
>=2.13.0+incompatible, <2.13.1+incompatible
2.13.1
2.12.4
2.4.0-rc1.0.20250331071157-dce7d9f5cffb
2.12.4+incompatible
2.13.1+incompatible

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-202 Exposure of Sensitive Information Through Data Queries

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.