Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2019-19025: 1.02% estimated exploitation activity in the next 30 days; percentile 63.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 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

Published by the source

18 May 2021, 18:27 UTC

Last modified by the source

6 Sep 2024, 21:54 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rffr-c932-cpxv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-19025

Advisory: Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor
IDs: CVE-2019-19025, GHSA-rffr-c932-cpxv
Record: https://patchnext.com/advisories/cve-2019-19025 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/goharbor/harbor 1.9.3, 1.8.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/goharbor/harbor: affected >= 1.7.0, < 1.8.6; >= 1.9.0, < 1.9.3; fixed in 1.8.6, 1.9.3

## Suggested inspection (read-only)
- Go github.com/goharbor/harbor: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/goharbor/harbor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rffr-c932-cpxv (GitHub-reviewed advisory GHSA-rffr-c932-cpxv lists affected ranges: Go github.com/goharbor/harbor >=1.7.0 =1.9.0 <1.9.3)

Commands are suggestions: review each one before running it.