fix(deps): update module github.com/sigstore/timestamp-authority/v2 to v2.1.0 [security] (alauda-v2.6.2) - #52
Open
alaudaa-renovate[bot] wants to merge 1 commit into
Conversation
…o v2.1.0 [security]
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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
1 participant
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.6->v2.1.0Sigstore 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).
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).
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
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 Renovate Bot.