Harbor fails to validate the user permissions when updating p2p preheat policies

Exploitation

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

CVSS

7.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

EPSS

• CVE-2022-31668: 0.30% estimated exploitation activity in the next 30 days; percentile 23.23 (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.

Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.

Published by the source

14 Nov 2024, 12:31 UTC

Last modified by the source

12 Dec 2024, 19:15 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r864-28pw-8682

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

# Patch Next advisory brief: CVE-2022-31668

Advisory: Harbor fails to validate the user permissions when updating p2p preheat policies
IDs: CVE-2022-31668, GHSA-r864-28pw-8682
Record: https://patchnext.com/advisories/cve-2022-31668 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
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/src 0.0.0-20220630175814-b4ef1db; github.com/goharbor/harbor 2.5.2, 2.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/goharbor/harbor/src: affected < 0.0.0-20220630175814-b4ef1db; fixed in 0.0.0-20220630175814-b4ef1db
- Go github.com/goharbor/harbor: affected >= 2.0.0, < 2.4.3; >= 2.5.0, < 2.5.2; fixed in 2.5.2, 2.4.3

## Suggested inspection (read-only)
- Go github.com/goharbor/harbor/src: check the installed version with your package manager.
- 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/src, 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-r864-28pw-8682 (GitHub-reviewed advisory GHSA-r864-28pw-8682 lists affected ranges: Go github.com/goharbor/harbor >=2.0.0 =2.5.0 =0 <0.0.0-20220630175814-b4ef1db)

Commands are suggestions: review each one before running it.