How severe is GHSA-rffr-c932-cpxv?

GHSA-rffr-c932-cpxv has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rffr-c932-cpxv?

GHSA-rffr-c932-cpxv affects the following packages: github.com/goharbor/harbor (Go), github.com/goharbor/harbor (Go). Ecosystems affected: Go.

How do I fix GHSA-rffr-c932-cpxv?

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

How do I detect GHSA-rffr-c932-cpxv in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rffr-c932-cpxv if there is no patch (or I can't update yet)?

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.

Is GHSA-rffr-c932-cpxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-rffr-c932-cpxv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rffr-c932-cpxv?

GHSA-rffr-c932-cpxv has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rffr-c932-cpxv?

GHSA-rffr-c932-cpxv is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rffr-c932-cpxv published, and has it been updated?

GHSA-rffr-c932-cpxv was published on May 18, 2021 and was last updated on September 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation HarborGHSA-rffr-c932-cpxv

HIGH

GHSA-rffr-c932-cpxv is a high-severity (CVSS 7.6) Cross-Site Request Forgery (CSRF) vulnerability in github.com/goharbor/harbor. A fix is available for github.com/goharbor/harbor — see the affected versions and patch details below.

Also known asCVE-2019-19025 GHSA-gcqm-v682-ccw6GO-2022-0876

Published

May 18, 2021

Updated

Sep 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-rffr-c932-cpxv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐹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

The vulnerability was immediately fixed by the Harbor team and all supported versions were patched.

Successful exploitation of this issue will lead to 3rd parties executing actions on the platform of behalf of authenticated users and administrators.

If your product uses the affected releases of Harbor, update to version 1.8.6 and 1.9.3 to patch this issue immediately.

https://github.com/goharbor/harbor/releases/tag/v1.8.6 https://github.com/goharbor/harbor/releases/tag/v1.9.3

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/goharbor/harbor`	≥ 1.7.0&&< 1.8.6	1.8.6`go get github.com/goharbor/harbor@v1.8.6`
🐹Go	`github.com/goharbor/harbor`	≥ 1.9.0&&< 1.9.3	1.9.3`go get github.com/goharbor/harbor@v1.9.3`

Affected Products

2 products · 3 configurations

Application

harborlinuxfoundation

≥ 1.9.0 && < 1.9.3

range

Application

vmware harbor registrypivotal

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/goharbor/harbor to 1.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rffr-c932-cpxv is resolved across your whole dependency graph.
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.

Frequently Asked Questions

Cure53 has discovered that the Harbor web interface does not implement protection mechanisms against Cross-Site Request Forgery (CSRF). By luring an authenticated user onto a prepared third-party website, an attacker can execute any action on the platform in the context of the currently authenticated victim. The vulnerability was immediately fixed by the Harbor team and all supported versions were patched. Successful exploitation of this issue will lead to 3rd parties executing actions on the platform of behalf of authenticated users and administrators. If your product uses the affected rel

O3 Security · Impact-Aware SCA

Is GHSA-rffr-c932-cpxv in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.6/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

harbor

7.4/10

Code-Review4/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

May 18, 2021

Last updated

Sep 6, 2024

Identifiers

GHSA-rffr-c932-cpxv

GHSA-gcqm-v682-ccw6

GO-2022-0876

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webtanzu.vmware.com

Related vulnerabilities

This CVE is high severity; 3 of 8 other CVEs affecting harbor are rated as high or higher (top: critical).

GHSA-prh4-vhfh-24mjCVE-2026-4404CVE-2025-32019CVE-2025-30086CVE-2022-31668CVE-2024-22278CVE-2024-22244CVE-2024-22261

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 6, 2024