CVE-2022-31669 is a medium severity authorization flaw in Harbor, scored 6.4. An authenticated user can update tag immutability policies in projects they have no access to. Upgrade to Harbor 2.4.3 or 2.5.2 or later; there is no workaround, so patching is the only fix.
What's affected
Harbor's advisory GHSA-8c6p-v837-77f6, published 29 August 2022, lists the Go module as affected in 2.x up to and including 2.4.2, and 2.5 up to and including 2.5.1. Patched versions are 2.4.3 and later in that line, and 2.5.2 and later. There are no workarounds. Researchers from Oxeye Security reported the issue.
The advisory describes an API call that updates an immutable tag rule by its ID. If the ID belongs to a project the caller cannot access, the call still modifies that project's rule.
Both GitHub and NVD give 6.4, rated Moderate by Harbor and Medium by NVD. The vector has network access, low privileges, changed scope, and low impact on integrity and availability. Confidentiality is not affected.
Compared with the sibling issues, this one's impact is that someone could weaken or remove rules that make tags immutable, or make rules that block legitimate pushes. The record's kev flag is false.
Weakness class per the record: CWE-285, CWE-863.
How to check if you're exposed
Find the Harbor version. The administration UI shows it, and the system information API reports it as harbor_version (it may need credentials depending on your setup):
curl -s https://harbor.example.com/api/v2.0/systeminfo
Replace the host name with your registry. Then compare the result with the patched versions above. If Harbor runs in Kubernetes, also check the image tags of the Harbor core component:
kubectl get pods -n harbor -o jsonpath='{.items[*].spec.containers[*].image}'
The free in-browser dependency scan at gold.safeguard.sh/scan can also help you see Harbor related components in a manifest you upload.
What to do now
- Inventory Harbor deployments and their versions.
- Upgrade to 2.5.2 or later, or to 2.4.3 or later if you must remain on 2.4.
- Audit tag immutability rules in each project and compare them with what the owners expect.
- Review who has accounts and project memberships on the registry.
Why it matters
Harbor is a registry, and in many companies it sits between build systems and production. Policies on tags, retention and image distribution protect what ships.
The flaw class is broken object level authorization. The API accepts an identifier for a policy, checks that you are logged in, and acts, without checking that the object belongs to a project you may change. Any authenticated user, including one with a low privileged role in one project, can reach other projects. That is why the advisory scores the scope as changed.
Tag immutability protects the promise that a tag like release or 1.4.2 always means the same image. Altering the rule means that promise can silently stop being true, which matters to anyone deploying by tag.
Quick check
Does this let someone read images in other projects?
The advisory describes modification of tag immutability policies and gives no confidentiality impact in its score.
Sources
Last reviewed: 19 October 2026.