Skip to content

Update module github.com/sigstore/timestamp-authority/v2 to v2.1.0 [SECURITY] (release-v0.8) - autoclosed - #1900

Closed
renovate[bot] wants to merge 1 commit into
release-v0.8from
renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability
Closed

renovate[bot] wants to merge 1 commit into
release-v0.8from
renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/sigstore/timestamp-authority/v2 v2.0.6 → v2.1.0 age adoption passing confidence
github.com/sigstore/timestamp-authority/v2 v2.0.4 → v2.1.0 age adoption passing confidence

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): 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.

This vulnerability does not apply to timestamp-authority service, only to users of timestamp-authority/v2/pkg/verification package.

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.

Patches

The issue will be fixed in timestamp-authority 2.0.6

Workarounds

Users of VerifyTimestampResponse can use the TSACertificate option 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 Score: 5.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

References

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 wrapMetrics middleware 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.7 or later.

Workarounds
  1. Block or drop incoming requests with invalid HTTP methods or unknown request paths at a reverse proxy or load balancer before they reach the timestamp authority server.
  2. Configure rate-limiting on the public interface to prevent remote attackers from issuing millions of unique requests in a short duration.

Severity

  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sigstore/timestamp-authority (github.com/sigstore/timestamp-authority/v2)

v2.1.0

Compare Source

What's Changed
  • Bound path and HTTP method metric label cardinality to prevent OOM in #​1374
  • Fix spec violations in policy, EKU, and hash verification in #​1375

Full Changelog: sigstore/timestamp-authority@v2.0.6...v2.1.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai

coderabbitai Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: fb920c40-f9be-4808-8d44-53bfd411485a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:39 PM UTC · Completed 2:45 PM UTC

Commit: b129283 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $3.36

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Oct 13, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine automated security dependency update from renovate[bot] touching only go.mod and go.sum files across main and acceptance modules; elevated dependency file count (>=2) and large blast radius are the primary Tier 1 drivers but are offset by bot authorship, absence of protected paths, and no CI changes — git history shows moderate churn consistent with active dependency management; anchored to prior score of 2 as all signals are unchanged.

Previous run

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine automated dependency update from renovate[bot] touching only go.mod and go.sum files; dependency file count (>=2) remains the primary Tier 1 driver, git history shows moderate churn consistent with active dependency management, offset by bot authorship and absence of protected paths or CI changes — anchored to prior score of 2 as signals are unchanged.

Previous run (2)

Risk Assessment: moderate (2/5)

Details

Routine automated dependency update from renovate[bot] touching only go.mod and go.sum files with no security-sensitive changes; elevated dependency file count (≥2) is the primary risk driver, offset by bot authorship and absence of protected paths or CI changes.

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Looks good to me

Previous run

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOltdfQ== -->

Looks good to me

Previous run (2)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOltdfQ== -->

Looks good to me

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 13, 2026
@renovate

renovate Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: acceptance/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 76 additional dependencies were updated

Details:

Package Change
cloud.google.com/go v0.121.6 -> v0.123.0
cloud.google.com/go/auth v0.18.0 -> v0.20.0
cloud.google.com/go/iam v1.5.3 -> v1.7.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp v1.30.0 -> v1.31.0
github.com/aws/aws-sdk-go-v2 v1.41.0 -> v1.41.7
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.7.1 -> v1.7.4
github.com/aws/aws-sdk-go-v2/config v1.32.5 -> v1.32.17
github.com/aws/aws-sdk-go-v2/credentials v1.19.5 -> v1.19.16
github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.18.16 -> v1.18.23
github.com/aws/aws-sdk-go-v2/internal/configsources v1.4.16 -> v1.4.23
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.7.16 -> v2.7.23
github.com/aws/aws-sdk-go-v2/internal/v4a v1.4.9 -> v1.4.24
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.13.4 -> v1.13.9
github.com/aws/aws-sdk-go-v2/service/internal/checksum v1.8.9 -> v1.9.7
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.13.16 -> v1.13.23
github.com/aws/aws-sdk-go-v2/service/internal/s3shared v1.19.9 -> v1.19.16
github.com/aws/aws-sdk-go-v2/service/s3 v1.88.3 -> v1.95.0
github.com/aws/aws-sdk-go-v2/service/signin v1.0.4 -> v1.0.11
github.com/aws/aws-sdk-go-v2/service/sso v1.30.7 -> v1.30.17
github.com/aws/aws-sdk-go-v2/service/ssooidc v1.35.12 -> v1.35.21
github.com/aws/aws-sdk-go-v2/service/sts v1.41.5 -> v1.42.1
github.com/aws/smithy-go v1.24.0 -> v1.25.1
github.com/clipperhouse/displaywidth v0.6.0 -> v0.10.0
github.com/clipperhouse/uax29/v2 v2.3.0 -> v2.6.0
github.com/cncf/xds/go v0.0.0-20251022180443-0feb69152e9f -> v0.0.0-20260202195803-dba9d589def2
github.com/envoyproxy/go-control-plane/envoy v1.35.0 -> v1.37.0
github.com/envoyproxy/protoc-gen-validate v1.2.1 -> v1.3.3
github.com/go-chi/chi/v5 v5.2.4 -> v5.2.5
github.com/go-jose/go-jose/v4 v4.1.3 -> v4.1.4
github.com/go-openapi/analysis v0.24.1 -> v0.25.0
github.com/go-openapi/errors v0.22.6 -> v0.22.7
github.com/go-openapi/jsonpointer v0.22.4 -> v0.23.1
github.com/go-openapi/jsonreference v0.21.4 -> v0.21.5
github.com/go-openapi/loads v0.23.2 -> v0.23.3
github.com/go-openapi/runtime v0.29.2 -> v0.31.0
github.com/go-openapi/spec v0.22.3 -> v0.22.4
github.com/go-openapi/strfmt v0.25.0 -> v0.26.2
github.com/go-openapi/swag v0.25.4 -> v0.26.0
github.com/go-openapi/swag/cmdutils v0.25.4 -> v0.26.0
github.com/go-openapi/swag/conv v0.25.4 -> v0.26.0
github.com/go-openapi/swag/fileutils v0.25.4 -> v0.26.0
github.com/go-openapi/swag/jsonname v0.25.4 -> v0.26.0
github.com/go-openapi/swag/jsonutils v0.25.4 -> v0.26.0
github.com/go-openapi/swag/loading v0.25.4 -> v0.26.0
github.com/go-openapi/swag/mangling v0.25.4 -> v0.26.0
github.com/go-openapi/swag/netutils v0.25.4 -> v0.26.0
github.com/go-openapi/swag/stringutils v0.25.4 -> v0.26.0
github.com/go-openapi/swag/typeutils v0.25.4 -> v0.26.0
github.com/go-openapi/swag/yamlutils v0.25.4 -> v0.26.0
github.com/go-openapi/validate v0.25.1 -> v0.25.2
github.com/go-viper/mapstructure/v2 v2.4.0 -> v2.5.0
github.com/googleapis/enterprise-certificate-proxy v0.3.9 -> v0.3.15
github.com/googleapis/gax-go/v2 v2.16.0 -> v2.22.0
github.com/letsencrypt/boulder v0.20251110.0 -> v0.20260223.0
github.com/olekukonko/errors v1.1.0 -> v1.2.0
github.com/olekukonko/ll v0.1.3 -> v0.1.6
github.com/olekukonko/tablewriter v1.1.2 -> v1.1.4
github.com/sigstore/sigstore v1.10.4 -> v1.10.6
go.opentelemetry.io/contrib/detectors/gcp v1.38.0 -> v1.42.0
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.63.0 -> v0.67.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.63.0 -> v0.67.0
go.opentelemetry.io/otel v1.39.0 -> v1.43.0
go.opentelemetry.io/otel/metric v1.39.0 -> v1.43.0
go.opentelemetry.io/otel/sdk v1.39.0 -> v1.43.0
go.opentelemetry.io/otel/sdk/metric v1.39.0 -> v1.43.0
go.opentelemetry.io/otel/trace v1.39.0 -> v1.43.0
go.opentelemetry.io/proto/otlp v1.7.1 -> v1.9.0
go.uber.org/zap v1.27.1 -> v1.28.0
golang.org/x/oauth2 v0.34.0 -> v0.36.0
golang.org/x/time v0.14.0 -> v0.15.0
google.golang.org/api v0.260.0 -> v0.277.0
google.golang.org/genproto v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260319201613-d00831a3d3e7
google.golang.org/genproto/googleapis/api v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260401024825-9d38bb4040a9
google.golang.org/genproto/googleapis/rpc v0.0.0-20260203192932-546029d2fa20 -> v0.0.0-20260427160629-7cedc36a6bc4
google.golang.org/grpc v1.78.0 -> v1.81.0
sigs.k8s.io/release-utils v0.12.3 -> v0.12.4
File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 18 additional dependencies were updated

Details:

Package Change
github.com/go-openapi/analysis v0.24.3 -> v0.25.0
github.com/go-openapi/jsonpointer v0.22.5 -> v0.23.1
github.com/go-openapi/runtime v0.29.3 -> v0.31.0
github.com/go-openapi/strfmt v0.26.1 -> v0.26.2
github.com/go-openapi/swag v0.25.5 -> v0.26.0
github.com/go-openapi/swag/cmdutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/conv v0.25.5 -> v0.26.0
github.com/go-openapi/swag/fileutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/jsonname v0.25.5 -> v0.26.0
github.com/go-openapi/swag/jsonutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/loading v0.25.5 -> v0.26.0
github.com/go-openapi/swag/mangling v0.25.5 -> v0.26.0
github.com/go-openapi/swag/netutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/stringutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/typeutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/yamlutils v0.25.5 -> v0.26.0
go.step.sm/crypto v0.77.2 -> v0.81.0
go.uber.org/zap v1.27.1 -> v1.28.0

@renovate
renovate Bot force-pushed the renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability branch from b129283 to d90c505 Compare October 13, 2026 20:56
@renovate
renovate Bot force-pushed the renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability branch 2 times, most recently from b4e7797 to c50e5a7 Compare October 24, 2026 15:08
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

🤖 Review · ⚠️ Cancelled · Started 3:10 PM UTC · Ended 3:13 PM UTC

Commit: c50e5a7 · View workflow run →

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Oct 24, 2026
@renovate
renovate Bot force-pushed the renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability branch from c50e5a7 to fd3481b Compare October 24, 2026 15:12
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 3:15 PM UTC · Completed 3:28 PM UTC

Commit: fd3481b · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.87

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review October 24, 2026 15:28

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 24, 2026
@renovate
renovate Bot force-pushed the renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability branch from fd3481b to a2df1c8 Compare October 26, 2026 10:11
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 10:13 AM UTC · Completed 10:26 AM UTC

Commit: a2df1c8 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.82

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Oct 26, 2026
@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review October 26, 2026 10:25

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 26, 2026
@renovate
renovate Bot force-pushed the renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability branch from a2df1c8 to a4c5627 Compare October 27, 2026 15:47
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 3:49 PM UTC · Completed 4:01 PM UTC

Commit: a4c5627 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $4.05

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Oct 27, 2026
@renovate renovate Bot changed the title Update module github.com/sigstore/timestamp-authority/v2 to v2.1.0 [SECURITY] (release-v0.8) Update module github.com/sigstore/timestamp-authority/v2 to v2.1.0 [SECURITY] (release-v0.8) - autoclosed Oct 27, 2026
@renovate renovate Bot closed this Oct 27, 2026
@renovate
renovate Bot deleted the renovate/release-v0.8-go-github.com-sigstore-timestamp-authority-v2-vulnerability branch October 27, 2026 15:59
@fullsend-ai-review

Copy link
Copy Markdown

Review skipped — this PR is already closed.

The /fs-review command only reviews open PRs/MRs.

Posted by fullsend post-review check

@fullsend-ai-retro

fullsend-ai-retro Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 4:01 PM UTC · Completed 4:13 PM UTC

Commit: a4c5627 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $6.75

@fullsend-ai-retro

Copy link
Copy Markdown

Retro: PR #1900 — ~$13 spent reviewing an autoclosed Renovate PR

PR #1900 was a Renovate bot security dependency update (sigstore/timestamp-authority/v2 v2.0.6 → v2.1.0) targeting the release-v0.8 branch, touching only go.mod and go.sum. Over 14 days (Oct 13–27), Renovate force-pushed the branch 6 times, triggering 5 review dispatches (1 cancelled). The 4 completed reviews all produced identical results: zero actionable findings, moderate risk, approve verdict. Total review cost: ~$13.10. The PR was autoclosed by Renovate on Oct 27 without merging — all review spend was wasted.

Run Date Cost Verdict
38414906438 Oct 13 $3.36 Approve
40105947385 Oct 24 $2.87 Approve
40305447311 Oct 26 $2.82 Approve
40534540289 Oct 27 $4.05 Approve

The final review (Oct 27) started at 15:49 UTC; the PR was autoclosed at 15:59 — during the review. The post-review script caught the closed state and posted a skip comment, but the $4.05 was already spent.

All findings covered by existing issues

Every improvement opportunity identified is already tracked by an open issue with active work:

Judge scores

Score Candidate Disposition
4 Skip review for Renovate bot PRs summary-only (covered by #1931 + PR #1932)
4 Skip re-review on bot rebases with clean prior approval summary-only (covered by fullsend-ai/fullsend#8830)
3 Debounce review runs on rapid force-pushes summary-only (covered by fullsend-ai/fullsend#4960)
3 Skip review dispatch for closed PRs summary-only (covered by fullsend-ai/fullsend#3010)
2 Skip challenger for info-only findings summary-only (covered by fullsend-ai/agents#841)

No new proposals filed — existing issues comprehensively cover all identified improvements. Merging PR #1932 would prevent this class of waste for Renovate PRs in conforma/policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants