# Harbor repository description page has Cross-site Scripting vulnerability in github.com/goharbor/harbor

Advisory record · `GHSA-f9vc-vf3r-pqqq`

- **Identifiers:** `GHSA-f9vc-vf3r-pqqq` · `BIT-harbor-2025-32019` · `CVE-2025-32019` · `GO-2025-3825`
- **State:** Confirmed
- **Severity:** CVSS 4.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 29 Jul 2025
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Jul 2025, 18:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/goharbor/harbor` (Go): affected `all versions || all versions || >=2.12.0-rc1+incompatible, <2.12.4-rc1+incompatible || >=2.13.0-rc1+incompatible, <2.13.1-rc1+incompatible`; fixed in `2.12.4-rc1+incompatible`, `2.13.1-rc1+incompatible`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The github.com/goharbor/harbor Go module has a cross-site scripting flaw on the repository description page in versions from 2.12.0-rc1 to before 2.12.4-rc1 and from 2.13.0-rc1 to before 2.13.1-rc1. The source also lists additional earlier versions and gives few details on what an attacker must do to exploit it. Upgrade to 2.12.4-rc1, 2.13.1-rc1, or a later release.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.1 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 31st percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jul 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-f9vc-vf3r-pqqq](https://github.com/advisories/GHSA-f9vc-vf3r-pqqq)
- [OSV: GHSA-f9vc-vf3r-pqqq](https://osv.dev/vulnerability/GHSA-f9vc-vf3r-pqqq)
- <https://github.com/goharbor/harbor/security/advisories/GHSA-f9vc-vf3r-pqqq>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-32019>
- <https://github.com/goharbor/harbor/commit/76c2c5f7cfd9edb356cbb373889a59cc3217a058>
- <https://github.com/goharbor/harbor/commit/a13a16383a41a8e20f524593cb290dc52f86f088>
- <https://github.com/goharbor/harbor/commit/f019430872118852f83f96cac9c587b89052d1e5>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f9vc-vf3r-pqqq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f9vc-vf3r-pqqq/>. Everything for agents: <https://agentprime.io/llms.txt>.
