Incorrect delegation lookups can make go-tuf download the wrong artifact

Exploitation

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

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-47534: 0.51% estimated exploitation activity in the next 30 days; percentile 43.32 (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.

During the ongoing work on the TUF conformance test suite, we have come across a test that reveals what we believe is a bug in go-tuf with security implications. The bug exists in go-tuf delegation tracing and could result in downloading the wrong artifact. We have come across this issue in the test in this PR: https://github.com/theupdateframework/tuf-conformance/pull/115. The test - testgraphtraversal - sets up a repository with a series of delegations, invokes the clients refresh() and then checks the order in which the client traced the delegations. The test shows that the go-tuf client inconsistently traces the delegations in a wrong way. For example, during one CI run, the two-level-delegations test case triggered a wrong order. The delegations in this look as such: Here, targets delegate to "A", and to "B", and "B" delegates to "C". The client should trace the delegations in the order "A" then "B" then "C" but in this particular CI run, go-tuf traced the delegations…

Published by the source

1 Oct 2024, 18:13 UTC

Last modified by the source

11 Oct 2024, 14:23 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4f8r-qqr9-fq8j

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

# Patch Next advisory brief: CVE-2024-47534

Advisory: Incorrect delegation lookups can make go-tuf download the wrong artifact
IDs: CVE-2024-47534, GHSA-4f8r-qqr9-fq8j
Record: https://patchnext.com/advisories/cve-2024-47534 (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 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/theupdateframework/go-tuf/v2 2.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/theupdateframework/go-tuf/v2: affected < 2.0.1; fixed in 2.0.1

## Suggested inspection (read-only)
- Go github.com/theupdateframework/go-tuf/v2: 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/theupdateframework/go-tuf/v2.
- 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-4f8r-qqr9-fq8j (GitHub-reviewed advisory GHSA-4f8r-qqr9-fq8j lists affected ranges: Go github.com/theupdateframework/go-tuf/v2 >=0 <2.0.1)

Commands are suggestions: review each one before running it.