Skip to content
Fencer Intel
medium 4.1

CVE-2025-32019 json

Harbor's repository description page allows for XSS

published last yr. modified 4mo ago also BIT-harbor-2025-32019 , EUVD-2025-22474 , GHSA-f9vc-vf3r-pqqq , GO-2025-3825

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

Summary

Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Versions 2.11.2 and below, as well as versions 2.12.0-rc1 and 2.13.0-rc1, contain a vulnerability where the markdown field in the info tab page can be exploited to inject XSS code. This is fixed in versions 2.11.3 and 2.12.3.

Patch / fix

  • go github.com/goharbor/harbor 2.4.0-rc1.0.20250421072404-a13a16383a41, 2.12.4-rc1, 2.12.4-rc1+incompatible, 2.13.1-rc1, 2.13.1-rc1+incompatible
  • bitnami harbor 2.11.3
  • linuxfoundation harbor 2.4.0-rc1.0.20250421072404-a13a16383a41, 2.11.3, 2.12.4-rc1, 2.13.1-rc1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1

opensuse advisories openSUSE-SU-2025:15405-1

Is CVE-2025-32019 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
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 4.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N
GitHub 3.1 4.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N
OSV 3.1 4.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/goharbor/harbor
>=2.12.0-rc1, <2.12.4-rc1
>=2.13.0-rc1, <2.13.1-rc1
>=2.4.0-rc1.1, <=2.11.2
<2.4.0-rc1.0.20250421072404-a13a16383a41
all versions
>=2.12.0-rc1+incompatible, <2.12.4-rc1+incompatible
>=2.13.0-rc1+incompatible, <2.13.1-rc1+incompatible
2.12.4-rc1
2.13.1-rc1
2.4.0-rc1.0.20250421072404-a13a16383a41
2.12.4-rc1+incompatible
2.13.1-rc1+incompatible
bitnami harbor
<2.11.3
2.11.3

Affected products

  • goharbor harbor

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.