Repository navigation
Update module github.com/sigstore/timestamp-authority/v2 to v2.1.0 [SECURITY] - autoclosed - #372
Closed
renovate-update-app[bot] wants to merge 1 commit into
Conversation
![renovatee-approver-stackvista[bot]](https://avatars.githubusercontent.com/u/10511829?s=60&v=4){kind=small}
renovate-update-app
Bot
changed the title
auto-merge was automatically disabled
October 26, 2026 08:35
Pull request was closed
renovate-update-app
Bot
deleted the
renovate/go-github.com-sigstore-timestamp-authority-v2-vulnerability
branch
October 26, 2026 08:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.0.3→v2.1.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Sigstore Timestamp Authority has Improper Certificate Validation in verifier
CVE-2026-39984 / GHSA-xm5m-wgh2-rrg3
More information
Details
Authorization bypass via certificate bag manipulation in sigstore/timestamp-authority verifier
An authorization bypass vulnerability exists in sigstore/timestamp-authority verifier (timestamp-authority/v2/pkg/verification):
VerifyTimestampResponsefunction correctly verifies the certificate chain but when the TSA specific constraints are verified inVerifyLeafCert, 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.This vulnerability does not apply to timestamp-authority service, only to users of
timestamp-authority/v2/pkg/verificationpackage.This vulnerability does not apply to sigstore-go even though it is a user of
timestamp-authority/v2/pkg/verification: ProvidingTSACertificateoption toVerifyTimestampResponsefully mitigates the issue.Patches
The issue will be fixed in timestamp-authority 2.0.6
Workarounds
Users of
VerifyTimestampResponsecan use theTSACertificateoption to specify the exact certificate they expect to be used: this fully mitigates the issue.References
This issue was found after reading CVE-2026-33753 / GHSA-3xxc-pwj6-jgrj (originally reported by @Jaynornj and @Pr00fOf3xpl0it)
Severity
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Sigstore Timestamp Authority has OOM due to unbounded metric label cardinality
CVE-2026-49835 / GHSA-9c54-x2g4-v92j
More information
Details
Impact
An unauthenticated remote attacker can trigger unbounded memory growth on the timestamp authority server.
This vulnerability exists because the global
wrapMetricsmiddleware records the raw HTTP request path (r.URL.Path) and raw HTTP request method (r.Method) as Prometheus labels for latency and request count metric vectors. Since this middleware runs before standard routing occurs, it executes for all incoming requests, including those for unmatched paths (yielding 404 responses) or arbitrary request methods. The Prometheus library registers a new, permanent time-series entry for every distinct label combination. An attacker can continuously issue requests containing random paths (e.g.,/api/v1/timestamp/<uuid>) or random HTTP methods to exhaust system memory.Patches
This issue has been patched by limiting the metric label values to a strict allowlist of expected paths (
/ping,/api/v1/timestamp,/api/v1/timestamp/certchain) and expected HTTP methods (GET,POST,HEAD,OPTIONS). Unrecognized paths or methods are normalized to a static string ("unrecognized").Users should update to version
v2.0.7or later.Workarounds
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Sigstore Timestamp Authority has Improper Certificate Validation in verifier
CVE-2026-39984 / GHSA-xm5m-wgh2-rrg3 / GO-2026-5763
More information
Details
Authorization bypass via certificate bag manipulation in sigstore/timestamp-authority verifier
An authorization bypass vulnerability exists in sigstore/timestamp-authority verifier (timestamp-authority/v2/pkg/verification):
VerifyTimestampResponsefunction correctly verifies the certificate chain but when the TSA specific constraints are verified inVerifyLeafCert, 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.This vulnerability does not apply to timestamp-authority service, only to users of
timestamp-authority/v2/pkg/verificationpackage.This vulnerability does not apply to sigstore-go even though it is a user of
timestamp-authority/v2/pkg/verification: ProvidingTSACertificateoption toVerifyTimestampResponsefully mitigates the issue.Patches
The issue will be fixed in timestamp-authority 2.0.6
Workarounds
Users of
VerifyTimestampResponsecan use theTSACertificateoption to specify the exact certificate they expect to be used: this fully mitigates the issue.References
This issue was found after reading CVE-2026-33753 / GHSA-3xxc-pwj6-jgrj (originally reported by @Jaynornj and @Pr00fOf3xpl0it)
Severity
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Sigstore Timestamp Authority has Improper Certificate Validation in verifier in github.com/sigstore/timestamp-authority
CVE-2026-39984 / GHSA-xm5m-wgh2-rrg3 / GO-2026-5763
More information
Details
Sigstore Timestamp Authority has Improper Certificate Validation in verifier in github.com/sigstore/timestamp-authority
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Sigstore Timestamp Authority has OOM due to unbounded metric label cardinality
CVE-2026-49835 / GHSA-9c54-x2g4-v92j / GO-2026-5851
More information
Details
Impact
An unauthenticated remote attacker can trigger unbounded memory growth on the timestamp authority server.
This vulnerability exists because the global
wrapMetricsmiddleware records the raw HTTP request path (r.URL.Path) and raw HTTP request method (r.Method) as Prometheus labels for latency and request count metric vectors. Since this middleware runs before standard routing occurs, it executes for all incoming requests, including those for unmatched paths (yielding 404 responses) or arbitrary request methods. The Prometheus library registers a new, permanent time-series entry for every distinct label combination. An attacker can continuously issue requests containing random paths (e.g.,/api/v1/timestamp/<uuid>) or random HTTP methods to exhaust system memory.Patches
This issue has been patched by limiting the metric label values to a strict allowlist of expected paths (
/ping,/api/v1/timestamp,/api/v1/timestamp/certchain) and expected HTTP methods (GET,POST,HEAD,OPTIONS). Unrecognized paths or methods are normalized to a static string ("unrecognized").Users should update to version
v2.0.7or later.Workarounds
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Sigstore Timestamp Authority has OOM due to unbounded metric label cardinality in github.com/sigstore/timestamp-authority
CVE-2026-49835 / GHSA-9c54-x2g4-v92j / GO-2026-5851
More information
Details
Sigstore Timestamp Authority has OOM due to unbounded metric label cardinality in github.com/sigstore/timestamp-authority
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
sigstore/timestamp-authority (github.com/sigstore/timestamp-authority/v2)
v2.1.0Compare Source
What's Changed
Full Changelog: sigstore/timestamp-authority@v2.0.6...v2.1.0
v2.0.6Compare Source
What's Changed
Full Changelog: sigstore/timestamp-authority@v2.0.5...v2.0.6
v2.0.5Compare Source
This release updates the chi middleware to resolve a panic.
Bug Fixes
Docs
Misc
v2.0.4Compare Source
Only contains dependency updates, but fixes #1252 due to breaking API change in sigstore/sigstore
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.