Summary
Impact
In the Harbor repository information, it is possible to inject code resulting in a stored XSS issue.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2025-32019 has a CVSS score of 4.1 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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.12.4-rc1, 2.13.1-rc1, 2.4.0-rc1.0.20250421072404-a13a16383a41); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Harbor v2.12.3 Harbor 2.11.3
Frequently Asked Questions
- What is CVE-2025-32019? CVE-2025-32019 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/goharbor/harbor (go), affecting versions >= 2.12.0-rc1, < 2.12.4-rc1. It is fixed in 2.12.4-rc1, 2.13.1-rc1, 2.4.0-rc1.0.20250421072404-a13a16383a41. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2025-32019? CVE-2025-32019 has a CVSS score of 4.1 (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.
- Which versions of github.com/goharbor/harbor are affected by CVE-2025-32019? github.com/goharbor/harbor (go) versions >= 2.12.0-rc1, < 2.12.4-rc1 is affected.
- Is there a fix for CVE-2025-32019? Yes. CVE-2025-32019 is fixed in 2.12.4-rc1, 2.13.1-rc1, 2.4.0-rc1.0.20250421072404-a13a16383a41. Upgrade to this version or later.
- Is CVE-2025-32019 exploitable, and should I be worried? Whether CVE-2025-32019 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
- What actually determines whether CVE-2025-32019 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.
- How do I fix CVE-2025-32019?
- Upgrade
github.com/goharbor/harborto 2.12.4-rc1 or later - Upgrade
github.com/goharbor/harborto 2.13.1-rc1 or later - Upgrade
github.com/goharbor/harborto 2.4.0-rc1.0.20250421072404-a13a16383a41 or later
- Upgrade