How severe is CVE-2022-31669?

CVE-2022-31669 has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-31669?

CVE-2022-31669 affects the following packages: github.com/goharbor/harbor (Go), github.com/goharbor/harbor (Go), github.com/goharbor/harbor (Go). Ecosystems affected: Go.

How do I fix CVE-2022-31669?

Update github.com/goharbor/harbor to 1.10.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31669 is resolved across your whole dependency graph.

How do I detect CVE-2022-31669 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 CVE-2022-31669 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-31669 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31669 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 CVE-2022-31669?

CVE-2022-31669 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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 CVE-2022-31669?

CVE-2022-31669 is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-31669 published, and has it been updated?

CVE-2022-31669 was published on November 14, 2024 and was last updated on October 28, 2026. 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

MEDIUM severity

CVE-2022-31669 — harbor

MEDIUM

CVE-2022-31669 is a medium-severity (CVSS 6.4) CWE-285 vulnerability in github.com/goharbor/harbor. A fix is available for github.com/goharbor/harbor — see the affected versions and patch details below.

Harbor fails to validate the user permissions when updating tag immutability policies

Also known asBIT-harbor-2022-31669GHSA-8c6p-v837-77f6

Published

Nov 14, 2024

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐹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

Harbor fails to validate the user permissions when updating tag immutability policies - API call:

PUT /projects/{project_name_or_id}/immutabletagrules/{immutable_rule_id}

By sending a request to update a tag immutability policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag immutability policies configured in other projects.

Patches

This and similar issues are fixed in Harbor v2.5.2 and later. Please upgrade as soon as possible.

Workarounds

There are no workarounds available.

For more information

If you have any questions or comments about this advisory:

Open an issue in the Harbor GitHub repository

Credits

Thanks to Gal Goldstein and Daniel Abeles from Oxeye Security for reporting this issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/goharbor/harbor`	≥ 1.0.0&&< 1.10.13	1.10.13`go get github.com/goharbor/harbor@v1.10.13`
🐹Go	`github.com/goharbor/harbor`	≥ 2.0.0&&< 2.4.3	2.4.3`go get github.com/goharbor/harbor@v2.4.3`
🐹Go	`github.com/goharbor/harbor`	≥ 2.5.0&&< 2.5.2	2.5.2`go get github.com/goharbor/harbor@v2.5.2`

Affected Products

1 product · 2 configurations

Application

harborlinuxfoundation

≥ 2.5.0 && < 2.5.2

range

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.10.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31669 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Harbor fails to validate the user permissions when updating tag immutability policies - API call: PUT /projects/{project_name_or_id}/immutabletagrules/{immutable_rule_id} By sending a request to update a tag immutability policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify tag immutability policies configured in other projects. ### Patches This and similar issues are fixed in Harbor v2.5.2 and later. Please upgrade as soon as possible. ### Workarounds There are no workarounds available. ### For mor

O3 Security · Impact-Aware SCA

Is CVE-2022-31669 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

None

Integrity

Low

Availability

Low

Raw vector

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

CWE Classification

CWE-285CWE-285 CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 14, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2022-31669

GHSA-8c6p-v837-77f6

BIT-harbor-2022-31669

References

Advisorygithub.com · CVE 2022 31669.json Advisorygithub.com · GHSA 8c6p v837 77f6 Advisorynvd.nist.gov · CVE 2022 31669 Packagegithub.com · harbor

Related vulnerabilities

This CVE is medium severity; 7 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 verifiedOct 28, 2026

CVE-2022-31669 — harbor

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

For more information

Credits

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-31669 in your dependencies?