Safeguard
Vulnerability Analysis•

CVE-2022-31670: High Missing Authorization in Harbor Tag Retention

CVE-2022-31670 lets a Harbor user modify tag retention policies in other projects, scored 7.7. Upgrade to Harbor 1.10.13, 2.4.3, 2.5.2 or later.

Safeguard Security Team
3 min read

CVE-2022-31670 is a high severity authorization flaw in Harbor, scored 7.7. An authenticated user can update tag retention policies in projects they cannot access. Upgrade to Harbor 1.10.13, 2.4.3 or 2.5.2 or later, depending on your release line. There is no workaround.

What's affected

Harbor's advisory GHSA-3637-v6vq-xqqw, published 29 August 2022, lists the Go module as affected in 1.x up to 1.10.12, 2.x up to 2.4.2 and 2.5 up to 2.5.1. Patched versions are 1.10.13 and later, 2.4.3 and later, and 2.5.2 and later. No workaround exists. This is the only one of the four Harbor advisories in this group that covers the 1.x line.

The advisory names an API call that updates a retention rule by ID. If the ID belongs to a project the user cannot access, the rule is still changed.

GitHub and NVD both score it 7.7 High. The vector is network, low privileges, changed scope, no confidentiality impact, high integrity impact and no availability impact. The record's kev flag is false.

The integrity rating is the highest of the group, with good reason: retention policies delete images on a schedule, so tampering can cause real data loss in another team's project.

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

  1. Locate Harbor instances and their versions, including old 1.x installs.
  2. Upgrade to 1.10.13, 2.4.3, 2.5.2 or later on your line.
  3. Review retention rules in every project, and check whether any images went missing unexpectedly.
  4. Make sure registry backups cover images that depend on retention, and restrict accounts to those who need them.

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.

Retention is the most sensitive of the four because a rule can quietly delete images. A malicious rule could expire the images a project depends on for rollback.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does the 1.x line have a fix?

Yes. The advisory lists 1.10.13 as patched for the 1.x line, alongside 2.4.3 and 2.5.2.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.