CVE-2026-6967
mediumpriority · track · 26OT risk · elevatedEPSS 0.003 · 17 %ileEUUSEPSS · scored 2026-10-28
Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users with delegated signing authority to bypass TUF specification integrity checks for delegated targets metadata and poison the local metadata cache, because load_delegations does not apply the same validation checks as the top-level targets metadata path. We recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.0.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–high · 3.9–7.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-4v58-8p28-2rq3awslabs/tough is Missing Delegated Metadata Validation2026-05-05ghsa · osvUS
### Summary Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users with delegated signing authority to bypass TUF specification integrity checks for delegated targets metadata and poison the local metadata cache, because load_delegations does not apply the same validation checks as the top-level targets metadata path. ### Impact The tough library, prior to 0.22.0, does not properly verify delegated target metadata. It allows someone with write access to the metadata to serve expired or otherwise invalid targets from a TUF repository which tough will then trust rather than reject. ### Impacted Versions: tough 0.9.0 through 0.21.x, tuftool through 0.14.x ### Patches This issue has been addressed in tough version 0.22.0 and tuftool version 0.15.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. ### Workarounds No workarounds to this issue are known. ### References * CVE-2026-6967 If there are any questions or comments about this advisory, please contact [AWS/Amazon] Security via the [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue. ### Acknowledgement Amazon Web Services Labs would like to thank Oleh Konko of 1seal for collaborating on this issue through the coordinated vulnerability disclosure process.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (14)
External citations — patches, advisories, analysis.
- https://github.com/awslabs/tough/releasesPatchcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2026-6967cnnvd
- https://aws.amazon.com/security/security-bulletins/2026-019-aws/enisa_euvd
- https://crates.io/crates/tough/0.22.0enisa_euvd
- https://crates.io/crates/tuftool/0.15.0enisa_euvd
- https://github.com/awslabs/tough/releases/tag/tough-v0.22.0enisa_euvd
- https://github.com/awslabs/tough/releases/tag/tuftool-v0.15.0enisa_euvd
- https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan