GHSA-66x3-6cw3-v5gj is a high-severity (CVSS 8) CWE-354 vulnerability in github.com/theupdateframework/go-tuf. A fix is available for github.com/theupdateframework/go-tuf — see the affected versions and patch details below.
Improper Validation of Integrity Check Value in go-tuf
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-66x3-6cw3-v5gj.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-66x3-6cw3-v5gj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/theupdateframework/go-tufReal-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
go-tuf does not correctly implement the client workflow for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to install software that is older than the software which the client previously knew to be available, and may include software with known vulnerabilities.
In more detail, the client code of go-tuf has several issues in regards to preventing rollback attacks:
- It does not take into account the content of any previously trusted metadata, if available, before proceeding with updating roles other than the root role (i.e., steps 5.4.3.1 and 5.5.5 of the detailed client workflow). This means that any form of version verification done on the newly-downloaded metadata is made using the default value of zero, which always passes.
- For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted before verifying if the version of the metafiles they refer to is correct (i.e., steps 5.5.4 and 5.6.4 of the detailed client workflow).
Patches
A fix is available in version 0.3.0 or newer.
Workarounds
No workarounds are known for this issue apart from upgrading.
References
- Commit resolving the issue https://github.com/theupdateframework/go-tuf/commit/ed6788e710fc3093a7ecc2d078bf734c0f200d8d
- TUF specification version against which this vulnerability is observed is v.1.0.28. For more details, refer to Section 5.
- Codebase that is affected is go-tuf@f0c3294f63b9145029464164f9bce49553b77cbb
For more information
If you have any questions or comments about this advisory:
- Open an issue in go-tuf
- Email us at TUF's mailing list
- The #tuf channel on CNCF Slack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/theupdateframework/go-tuf | all versions | 0.3.0go get github.com/theupdateframework/go-tuf@v0.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/theupdateframework/go-tuf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/theupdateframework/go-tuf to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66x3-6cw3-v5gj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-66x3-6cw3-v5gj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-66x3-6cw3-v5gj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| RHACS-3.71-RHEL-8 | advanced-cluster-security/rhacs-docs-rhel8:3.71.0-5 | RHSA-2022:5704 |
Frequently Asked Questions
Is GHSA-66x3-6cw3-v5gj in your dependencies?
O3 Security finds GHSA-66x3-6cw3-v5gj across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.