https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:16:05 +0000 https://cve.radiocsirt.org/vuln/brew-sigstore-cve-2025-52556 <p><strong>Affected:</strong> Homebrew: sigstore</p> <p>### Impact</p> <p>`rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR&#39;s embedded certificates up to the trusted root(s), but fails to verify the TSR&#39;s own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA.</p> <p>### Patches</p> <p>Users should immediately upgrade to `rfc3161-client` 1.0.3 or later.</p> <p>### Workarounds</p> <p>There is no workaround possible. Users should immediately upgrade to a fixed version.</p> <p><strong>Affected:</strong> Homebrew: sigstore</p> <p>### Impact</p> <p>`rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR&#39;s embedded certificates up to the trusted root(s), but fails to verify the TSR&#39;s own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA.</p> <p>### Patches</p> <p>Users should immediately upgrade to `rfc3161-client` 1.0.3 or later.</p> <p>### Workarounds</p> <p>There is no workaround possible. Users should immediately upgrade to a fixed version.</p> https://cve.radiocsirt.org/vuln/brew-sigstore-cve-2025-52556 https://cve.radiocsirt.org/vuln/cve-2025-52556 <p><strong>Affected:</strong> trailofbits rfc3161-client</p> <p>rfc3161-client is a Python library implementing the Time-Stamp Protocol (TSP) described in RFC 3161. Prior to version 1.0.3, there is a flaw in the timestamp response signature verification logic. In particular, chain verification is performed against the TSR&#39;s embedded certificates up to the trusted root(s), but fails to verify the TSR&#39;s own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce any TSR signature so long as the embedded leaf chains up to some root TSA. This issue has been patched in version 1.0.3. There is no workaround for this issue.</p> <p><strong>Affected:</strong> trailofbits rfc3161-client</p> <p>rfc3161-client is a Python library implementing the Time-Stamp Protocol (TSP) described in RFC 3161. Prior to version 1.0.3, there is a flaw in the timestamp response signature verification logic. In particular, chain verification is performed against the TSR&#39;s embedded certificates up to the trusted root(s), but fails to verify the TSR&#39;s own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce any TSR signature so long as the embedded leaf chains up to some root TSA. This issue has been patched in version 1.0.3. There is no workaround for this issue.</p> https://cve.radiocsirt.org/vuln/cve-2025-52556 https://cve.radiocsirt.org/vuln/ghsa-6qhv-4h7r-2g9m <p><strong>Affected:</strong> PyPI: rfc3161-client</p> <p>### Impact</p> <p>`rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR&#39;s embedded certificates up to the trusted root(s), but fails to verify the TSR&#39;s own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA.</p> <p>### Patches</p> <p>Users should immediately upgrade to `rfc3161-client` 1.0.3 or later.</p> <p>### Workarounds</p> <p>There is no workaround possible. Users should immediately upgrade to a fixed version.</p> <p><strong>Affected:</strong> PyPI: rfc3161-client</p> <p>### Impact</p> <p>`rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR&#39;s embedded certificates up to the trusted root(s), but fails to verify the TSR&#39;s own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA.</p> <p>### Patches</p> <p>Users should immediately upgrade to `rfc3161-client` 1.0.3 or later.</p> <p>### Workarounds</p> <p>There is no workaround possible. Users should immediately upgrade to a fixed version.</p> https://cve.radiocsirt.org/vuln/ghsa-6qhv-4h7r-2g9m