https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 16:27:06 +0000 https://vulnerability.circl.lu/vuln/ghsa-xm5m-wgh2-rrg3 <p><strong>Affected:</strong> Go: github.com/sigstore/timestamp-authority/v2</p> <p>### Authorization bypass via certificate bag manipulation in sigstore/timestamp-authority verifier</p> <p>An authorization bypass vulnerability exists in sigstore/timestamp-authority verifier (timestamp-authority/v2/pkg/verification): `VerifyTimestampResponse` function correctly verifies the certificate chain but when the TSA specific constraints are verified in `VerifyLeafCert`, the first non-CA certificate from the PKCS#7 certificate bag is used instead of the leaf certificate from the certificate chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key. The library validates the signature using the one certificate but performs authorization checks on the another, allowing an attacker to bypass some authorization controls.</p> <p>This vulnerability does **not** apply to timestamp-authority service, only to users of `timestamp-authority/v2/pkg/verification` package.</p> <p>This vulnerability does **not** apply to sigstore-go even though it is a user of `timestamp-authority/v2/pkg/verification`: Providing `TSACertificate` option to `VerifyTimestampResponse` fully mitigates the issue.</p> <p>### Patches</p> <p>The issue will be fixed in timestamp-authority 2.0.6</p> <p>### Workarounds</p> <p>Users of `VerifyTimestampResponse` can use the `TSACertificate` option to specify the exact certificate they expect to be used: this fully mitigates the issue.</p> <p>### References</p> <p>This issue was found after reading CVE-2026-33753 / GHSA-3xxc-p…</p> <p><strong>Affected:</strong> Go: github.com/sigstore/timestamp-authority/v2</p> <p>### Authorization bypass via certificate bag manipulation in sigstore/timestamp-authority verifier</p> <p>An authorization bypass vulnerability exists in sigstore/timestamp-authority verifier (timestamp-authority/v2/pkg/verification): `VerifyTimestampResponse` function correctly verifies the certificate chain but when the TSA specific constraints are verified in `VerifyLeafCert`, the first non-CA certificate from the PKCS#7 certificate bag is used instead of the leaf certificate from the certificate chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key. The library validates the signature using the one certificate but performs authorization checks on the another, allowing an attacker to bypass some authorization controls.</p> <p>This vulnerability does **not** apply to timestamp-authority service, only to users of `timestamp-authority/v2/pkg/verification` package.</p> <p>This vulnerability does **not** apply to sigstore-go even though it is a user of `timestamp-authority/v2/pkg/verification`: Providing `TSACertificate` option to `VerifyTimestampResponse` fully mitigates the issue.</p> <p>### Patches</p> <p>The issue will be fixed in timestamp-authority 2.0.6</p> <p>### Workarounds</p> <p>Users of `VerifyTimestampResponse` can use the `TSACertificate` option to specify the exact certificate they expect to be used: this fully mitigates the issue.</p> <p>### References</p> <p>This issue was found after reading CVE-2026-33753 / GHSA-3xxc-p…</p> https://vulnerability.circl.lu/vuln/ghsa-xm5m-wgh2-rrg3