https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-12T19:32:12.460679+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-292978 EUVD-2026-292978 2026-10-12T19:32:12.463088+00:00 EUVD-2026-292978 https://cve.radiocsirt.org/vuln/fkie_cve-2026-6967 fkie_cve-2026-6967 2026-10-12T19:32:12.463118+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-4v58-8p28-2rq3 GHSA-4v58-8p28-2rq3 — awslabs/tough is Missing Delegated Metadata Validation 2026-10-12T19:32:12.463151+00:00

Affected: crates.io: tough, crates.io: tuftool

### 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 collaborat…