https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 19:30:41 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-254883 EUVD-2026-254883 https://cve.radiocsirt.org/vuln/euvd-2026-254883 https://cve.radiocsirt.org/vuln/fkie_cve-2025-2888 <p>During a snapshot rollback, the client incorrectly caches the timestamp metadata. If the client checks the cache when attempting to perform the next update, the update timestamp validation will fail, preventing the next update until the cache is cleared. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.</p> <p>During a snapshot rollback, the client incorrectly caches the timestamp metadata. If the client checks the cache when attempting to perform the next update, the update timestamp validation will fail, preventing the next update until the cache is cleared. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-2888 https://cve.radiocsirt.org/vuln/ghsa-76g3-38jv-wxh4 <p><strong>Affected:</strong> crates.io: tough</p> <p>## Summary</p> <p>TUF repositories use the timestamp role to protect against rollback events by enabling an automated process to periodically sign the role&#39;s metadata. While tough will ensure that the version of snapshot metadata in new timestamp metadata files was always greater than or equal to the previously trusted version, it will only do so after persisting the timestamp metadata to its cache.</p> <p>## Impact</p> <p>If the tough client successfully detects a rollback event in which timestamp metadata contains outdated snapshot metadata, the invalid timestamp metadata will still be persisted to cache as trusted. tough may then subsequently incorrectly identify valid timestamp metadata as being rolled back, preventing the client from consuming valid updates.</p> <p>Impacted versions: &lt; v0.20.0</p> <p>## Patches</p> <p>A fix for this issue is available in tough version 0.20.0 and later. Customers are advised to upgrade to version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.</p> <p>## Workarounds</p> <p>There is no recommended work around. Customers are advised to upgrade to version 0.20.0 or the latest version.</p> <p>## References</p> <p>If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p> <p>[1] Vulnerability reporting page: https://aws.amazon.com/security/vulner…</p> <p><strong>Affected:</strong> crates.io: tough</p> <p>## Summary</p> <p>TUF repositories use the timestamp role to protect against rollback events by enabling an automated process to periodically sign the role&#39;s metadata. While tough will ensure that the version of snapshot metadata in new timestamp metadata files was always greater than or equal to the previously trusted version, it will only do so after persisting the timestamp metadata to its cache.</p> <p>## Impact</p> <p>If the tough client successfully detects a rollback event in which timestamp metadata contains outdated snapshot metadata, the invalid timestamp metadata will still be persisted to cache as trusted. tough may then subsequently incorrectly identify valid timestamp metadata as being rolled back, preventing the client from consuming valid updates.</p> <p>Impacted versions: &lt; v0.20.0</p> <p>## Patches</p> <p>A fix for this issue is available in tough version 0.20.0 and later. Customers are advised to upgrade to version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.</p> <p>## Workarounds</p> <p>There is no recommended work around. Customers are advised to upgrade to version 0.20.0 or the latest version.</p> <p>## References</p> <p>If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p> <p>[1] Vulnerability reporting page: https://aws.amazon.com/security/vulner…</p> https://cve.radiocsirt.org/vuln/ghsa-76g3-38jv-wxh4