Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-f9vc-vf3r-pqqq

MEDIUM

Harbor repository description page has Cross-site Scripting vulnerability

Also known asBIT-harbor-2025-32019CVE-2025-32019GO-2025-3825
Published
Jul 23, 2025
Updated
Jul 29, 2025
Affected
4 pkgs
Patched
3 / 4
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk22th percentile+0.14%
0.00%0.27%0.54%0.80%0.1%0.3%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

In the Harbor repository information, it is possible to inject code resulting in a stored XSS issue.

Patches

Harbor v2.12.3 Harbor 2.11.3

Workarounds

No

References

Credit

[email protected]

Affected Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/goharbor/harbor2.12.0-rc1&&< 2.12.4-rc12.12.4-rc1
🐹Gogithub.com/goharbor/harbor2.13.0-rc1&&< 2.13.1-rc12.13.1-rc1
🐹Gogithub.com/goharbor/harbor2.4.0-rc1.1No fix
🐹Gogithub.com/goharbor/harborall versions2.4.0-rc1.0.20250421072404-a13a16383a41

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/goharbor/harbor to 2.12.4-rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9vc-vf3r-pqqq is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-f9vc-vf3r-pqqq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f9vc-vf3r-pqqq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In the Harbor repository information, it is possible to inject code resulting in a stored XSS issue. ### Patches Harbor v2.12.3 Harbor 2.11.3 ### Workarounds No ### References ### Credit [email protected]
O3 Security · Impact-Aware SCA

Is GHSA-f9vc-vf3r-pqqq in your dependencies?

O3 detects GHSA-f9vc-vf3r-pqqq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.