Every CVE Search/ Get API key

CVE-2026-39984

Sigstore Timestamp Authority has Improper Certificate Validation in verifier

5.5 MediumFix available

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
None
User interaction
Required

What an attacker can affect

Confidentiality
None
Integrity
High
Availability
None

Exploit likelihood

0.10%Up 0.1 points since Apr 15, 2026
90%50%10%1%

What each source reports

CVE List Score used 5.5

Sigstore Timestamp Authority has Improper Certificate Validation in verifier

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Record
CVE-2026-39984
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
EUVDEUVD-2026-22813 5.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Record
EUVD-2026-22813
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-xm5m-wgh2-rrg3 5.5

Sigstore Timestamp Authority has Improper Certificate Validation in verifier

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)

Record
GHSA-xm5m-wgh2-rrg3
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
NVD 5.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Record
CVE-2026-39984
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
OSV 5.5

Sigstore Timestamp Authority has Improper Certificate Validation in verifier

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Record
CVE-2026-39984
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
OSVDEBIAN-CVE-2026-39984 5.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Record
DEBIAN-CVE-2026-39984
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Updated
2026-11-02
Show 20 moreShow less
OSVGHSA-xm5m-wgh2-rrg3 5.5

Sigstore Timestamp Authority has Improper Certificate Validation in verifier

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)

Record
GHSA-xm5m-wgh2-rrg3
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
OSVUBUNTU-CVE-2026-39984 5.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Record
UBUNTU-CVE-2026-39984
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Updated
2026-11-02
OSVGO-2026-5763 No score

Sigstore Timestamp Authority has Improper Certificate Validation in verifier in github.com/sigstore/timestamp-authority

Sigstore Timestamp Authority has Improper Certificate Validation in verifier in github.com/sigstore/timestamp-authority

Record
GO-2026-5763
Updated
2026-11-02
OSVopenSUSE-SU-2026:10651-1 No score

trivy-0.70.0-1.1 on GA media

These are all security issues fixed in the trivy-0.70.0-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2026:10651-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:10702-1 No score

hauler-1.4.3-1.1 on GA media

These are all security issues fixed in the hauler-1.4.3-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2026:10702-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:11144-1 No score

docker-29.4.0_ce-40.1 on GA media

These are all security issues fixed in the docker-29.4.0_ce-40.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2026:11144-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:20702-1 No score

Security update for trivy

This update for trivy fixes the following issues:

Changes in trivy:

  • Update to version 0.70.0 ( bsc#1260193, CVE-2026-33186, bsc#1260971, CVE-2026-33747, bsc#1261052, CVE-2026-33748, bsc#1262389, CVE-2026-39984, bsc#1262893, CVE-2026-34986):
    • release: v0.70.0 [main] (#10105)
    • chore(deps): bump go.opentelemetry.io/otel/sdk from 1.42.0 to 1.43.0 (#10496)
    • chore(deps): bump github.com/sigstore/timestamp-authority/v2 from 2.0.3 to 2.0.6 (#10526)
    • chore(deps): bump the common group across 1 directory with 8 updates (#10540)
    • chore(deps): bump the docker group across 1 directory with 2 updates (#10538)
    • fix: use Development category for GoReleaser discussions (#10530)
    • chore(deps): bump testcontainers-go to v0.42.0 (#10531)
    • chore: update CODEOWNERS (#10529)
    • chore(deps): bump helm.sh/helm/v3 from 3.20.1 to 3.20.2 (#10511)
    • chore(deps): bump github.com/hashicorp/go-getter from 1.8.5 to 1.8.6 (#10510)
    • chore(deps): bump github.com/moby/buildkit from 0.27.1 to 0.28.1 (#10449)
    • ci: migrate from mkdocs-material-insiders to mkdocs-material (#10509)
    • chore: remove aquasecurity/homebrew-trivy tap from GoReleaser (#10508)
    • ci: update runners for workflows that interact with GitHub API (#10502)
    • ci: rename tokens and update runners (#10500)
    • ci: trigger helm chart publishing via helm-charts workflow (#10474)
    • ci: remove ruleset update step from release-please workflow (#10499)
    • ci: use large runner and replace ORG_REPO_TOKEN in release-please workflow (#10498)
    • ci: trigger rpm/deb deployment via trivy-repo workflow (#10476)
    • fix: remove os.Stdout from wazero module config (#10403)
    • chore(deps): bump the common group across 1 directory with 22 updates (#10408)
    • chore(deps): bump google.golang.org/grpc from 1.78.0 to 1.79.3 (#10407)
    • fix(flag): validate template file extension (#10296)
    • fix(sbom): preserve Red Hat BuildInfo when scanning SBOMs without layer info (#10378)
    • fix: handle Go 1.26 GOEXPERIMENT version format change (#10351)
    • fix(python): handle multiple version specifiers in requirements.txt (#10361)
    • ci: run Trivy version bump in trivy-action (#10272)
    • fix(python): nil pointer dereference with optional poetry groups without dependencies (#10359)
    • ci: replace personal email with github-actions[bot] in workflows (#10369)
    • chore: replace smithy epoch parsing with stdlib time.Unix (#10286)
    • test: update golden files for purl changes (#10372)
    • ci: add zizmor to scan GitHub Actions workflows (#10322)
    • refactor: log statuses as strings (#10285)
    • ci: add build provenance attestations for release artifacts (#10316)
    • fix(sbom): add NOASSERTION for licenseDeclared/licenseConcluded in SPDX non-library packages (#10368)
    • fix(report): set correct sarif ROOTPATH uri when scanning a git repository (#10366)
    • perf(plugin): optimize directory traversal by replacing filepath.Walk with filepath.WalkDir (#10325)
    • docs: correct typos in CHANGELOG and diagram (#10320)
    • chore: delete roadmap wf (#10295)
    • ci(helm): bump Trivy version to 0.69.3 for Trivy Helm Chart 0.21.3 (#10310)
    • fix(cyclonedx): include CVSS v4 vulnerability ratings (#10313)
    • fix: detected vulnerability fields in azure and mariner detector (#10275)
    • ci: add persist-credentials: false to checkout steps (#10306)
    • ci(helm): bump Trivy version to 0.69.2 for Trivy Helm Chart 0.21.2 (#10270)
    • chore(deps): bump the common group across 1 directory with 8 updates (#10248)
    • chore(deps): bump go.opentelemetry.io/otel/sdk from 1.39.0 to 1.40.0 (#10257)
    • chore(deps): bump the aws group across 1 directory with 6 updates (#10249)
    • chore(deps): bump github.com/cloudflare/circl from 1.6.1 to 1.6.3 (#10241)
    • ci: remove apidiff workflow (#10259)
    • chore(deps): bump github.com/docker/cli from 29.1.4+incompatible to 29.2.1+incompatible in the docker group across 1 directory (#10221)
    • ci: bump golangci-lint to v2.10 in…
Record
openSUSE-SU-2026:20702-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:20711-1 No score

Security update for hauler

This update for hauler fixes the following issues:

Changes in hauler:

  • update to 1.4.3 ( bsc#1262353, CVE-2026-39984, bsc#1262942, CVE-2026-34986):
    • [1.4] Bump go.opentelemetry.io/otel/sdk from 1.40.0 to 1.43.0 in the go_modules group across 1 directory
    • [1.4] Bump github.com/sigstore/timestamp-authority/v2 from 2.0.4 to 2.0.6 in the go_modules group across 1 directory
    • [1.4] Bump google.golang.org/grpc from 1.78.0 to 1.79.3 in the go_modules group across 1 directory
    • fixed versions and dependencies on release/1.4
    • [1.4] removed unnecessary rewrite flag from sync
    • added makefile command for vulnerability checks (backport #577)
    • remove cherrypick bot and add mergify details (backport #581)
Record
openSUSE-SU-2026:20711-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:20809-1 No score

Security update for trivy

This update for trivy fixes the following issues

  • CVE-2025-64702: github.com/quic-go/quic-go/http3: quic-go HTTP/3 QPACK Header Expansion DoS (bsc#1255366).
  • CVE-2025-69725: github.com/go-chi/chi/v5: incorrect input validation in the RedirectSlashes function can lead to an open redirect (bsc#1258513).
  • CVE-2026-25934: github.com/go-git/go-git/v5: improper verification of data integrity values for .pack and .idx files can lead to the consumption of corrupted files (bsc#1258094).
  • CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260193).
  • CVE-2026-33747: github.com/moby/buildkit: malicious frontends can craft API messages that cause files to be written outside of the BuildKit state directory (bsc#1260971).
  • CVE-2026-33748: github.com/moby/buildkit: insufficient validation of Git URL fragment subdir components may allow access to files outside the checked-out Git repository (bsc#1261052).
  • CVE-2026-34986: github.com/go-jose/go-jose/v4: crafted JWE input with a missing encrypted key can lead to a denial of service (bsc#1262893).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262389).
  • CVE-2026-41506: github.com/go-git/go-git/v5: HTTP authentication credential leak when following redirects during smart-HTTP clone and fetch operations (bsc#1264873).

Changes for trivy:

  • Updated go-git to 5.18.0.
  • Updated to version 0.70.0.
Record
openSUSE-SU-2026:20809-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:21060-1 No score

Security update for docker

This update for docker fixes the following issues

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Record
openSUSE-SU-2026:21060-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
  • GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
  • GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
  • GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
  • GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
  • GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
  • GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
  • GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
  • GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
  • GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
  • GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
  • GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
  • GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
  • GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
  • GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
  • GO-2026-5933 GHSA-3g4q-2f67-2gvh
  • GO-2026-5934 GHSA-59qp-cfj3-rp64
  • GO-2026-5935 GHSA-7856-g3gv-9wq8
  • GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
  • GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
  • GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
  • GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
  • GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
  • GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
  • GO-2026-5942 CVE-2026-46600
  • GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
  • GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
  • GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
  • GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
  • GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
  • GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
  • GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
  • GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
  • GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
  • GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
  • GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
  • GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
  • GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
  • GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
  • GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
  • GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
  • GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
  • GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
  • GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
  • GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
  • GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
  • GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
  • GO-2026-5969 GHSA-g936-7jqj-mwv8
  • GO-2026-5970 CVE-2026-56852
  • GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
  • GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
  • GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
  • GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
  • GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
  • GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
  • GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
  • GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
  • GO-2026-5981 GHSA-mqxv-9rm6-w8qc
  • GO-2026-5982 GHSA-pqg7-v6wh-3pfp
  • GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
  • GO-2026-5985 GHSA-7rx3-5wx3-5v76
  • GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
  • GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
  • GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
  • GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
  • GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
  • GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
  • GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
  • GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
  • GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
  • GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
  • GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
  • GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
  • GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
  • GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
  • GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
  • GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
Record
openSUSE-SU-2026:21483-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:22158-1 No score

Security update for docker

This update for docker fixes the following issues:

Security issues fixed:

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).

Non security issue fixed:

  • SELinux CIL files are not shipped in Docker (bsc#1278193).

Changes for docker:

Record
openSUSE-SU-2026:22158-1
Updated
2026-11-02
OSVSUSE-SU-2026:22285-1 No score

Security update for docker

This update for docker fixes the following issues

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Record
SUSE-SU-2026:22285-1
Updated
2026-11-02
OSVSUSE-SU-2026:22367-1 No score

Security update for docker

This update for docker fixes the following issues

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Record
SUSE-SU-2026:22367-1
Updated
2026-11-02
OSVSUSE-SU-2026:22456-1 No score

Security update for docker

This update for docker fixes the following issues

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Record
SUSE-SU-2026:22456-1
Updated
2026-11-02
OSVSUSE-SU-2026:22513-1 No score

Security update for docker

This update for docker fixes the following issues

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Record
SUSE-SU-2026:22513-1
Updated
2026-11-02
OSVSUSE-SU-2026:24279-1 No score

Security update for docker

This update for docker fixes the following issues:

Security issues fixed:

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).

Non security issue fixed:

  • SELinux CIL files are not shipped in Docker (bsc#1278193).

Changes for docker:

Record
SUSE-SU-2026:24279-1
Updated
2026-11-02
OSVSUSE-SU-2026:24318-1 No score

Security update for docker

This update for docker fixes the following issues:

Security issues fixed:

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).

Non security issue fixed:

  • SELinux CIL files are not shipped in Docker (bsc#1278193).

Changes for docker:

Record
SUSE-SU-2026:24318-1
Updated
2026-11-02
OSVSUSE-SU-2026:24410-1 No score

Security update for docker

This update for docker fixes the following issues:

Security issues fixed:

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).

Non security issue fixed:

  • SELinux CIL files are not shipped in Docker (bsc#1278193).

Changes for docker:

Record
SUSE-SU-2026:24410-1
Updated
2026-11-02
OSVSUSE-SU-2026:2692-1 No score

Security update for docker

This update for docker fixes the following issues

  • CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
  • CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
  • CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
  • CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Record
SUSE-SU-2026:2692-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/sigstore/timestamp-authority/v2
Go
 through 2.0.5
2.0.6
golang-github-sigstore-timestamp-authority
Debian:13
 All versions, plus listed versions
1.2.3-21.2.9-12.0.3-12.0.3-22.0.4-1
Show 4 moreShow less
2.1.0-12.1.2-12.1.3-12.1.3-2
 None known
golang-github-sigstore-timestamp-authority
Debian:14
 before 2.1.0-1, plus listed versions
1.2.3-21.2.9-12.0.3-12.0.3-22.0.4-1
2.1.0-1
github.com/sigstore/timestamp-authority/v2
Go
 before 2.0.6
2.0.6
github.com/sigstore/timestamp-authority
Go
 All versions None known
docker
SUSE:Linux Micro 6.2
 before 29.4.0_ce-160000.7.1
29.4.0_ce-160000.7.1
docker
SUSE:Linux Enterprise Server 16.0
 before 29.4.0_ce-160000.7.1
29.4.0_ce-160000.7.1
docker
SUSE:Linux Enterprise Server for SAP applications 16.0
 before 29.4.0_ce-160000.7.1
29.4.0_ce-160000.7.1
docker
SUSE:Linux Micro 6.1
 before 29.4.0_ce-slfo.1.1_10.1
29.4.0_ce-slfo.1.1_10.1
docker
SUSE:Linux Micro 6.0
 before 29.4.0_ce-11.1
29.4.0_ce-11.1
Show 27 moreShow less
Affected packages
PackageAffectedFixed
docker
SUSE:Linux Micro 6.1
 before 29.7.2_ce-slfo.1.1_11.1
29.7.2_ce-slfo.1.1_11.1
docker
SUSE:Linux Micro 6.0
 before 29.7.2_ce-159998.1.1
29.7.2_ce-159998.1.1
docker
SUSE:Linux Micro 6.2
 before 29.7.2_ce-160000.8.1
29.7.2_ce-160000.8.1
docker
SUSE:Linux Enterprise Micro 5.3
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Micro 5.4
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Micro 5.5
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Module for Basesystem 15 SP7
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Module for Containers 15 SP7
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Server 15 SP4-LTSS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Server 15 SP5-LTSS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Server 15 SP6-LTSS
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Server for SAP Applications 15 SP4
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Server for SAP Applications 15 SP5
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
docker
SUSE:Linux Enterprise Server for SAP Applications 15 SP6
 before 29.4.0_ce-150000.253.1
29.4.0_ce-150000.253.1
golang-github-sigstore-timestamp-authority
Ubuntu:25.10
 All versions, plus listed versions
1.2.3-2
 None known
golang-github-sigstore-timestamp-authority
Ubuntu:26.10
 All versions, plus listed versions
2.0.4-12.1.3-2
 None known
golang-github-sigstore-timestamp-authority
Ubuntu:26.04:LTS
 All versions, plus listed versions
1.2.3-21.2.9-12.0.3-22.0.4-1
 None known
trivy
openSUSE:Tumbleweed
 before 0.70.0-1.1
0.70.0-1.1
hauler
openSUSE:Tumbleweed
 before 1.4.3-1.1
1.4.3-1.1
docker
openSUSE:Tumbleweed
 before 29.4.0_ce-40.1
29.4.0_ce-40.1
docker
openSUSE:Leap 16.0
 before 29.4.0_ce-160000.7.1
29.4.0_ce-160000.7.1
govulncheck-vulndb
openSUSE:Leap 16.0
 before 0.0.20260723T184607-160000.1.1
0.0.20260723T184607-160000.1.1
docker
openSUSE:Leap 16.0
 before 29.7.2_ce-160000.8.1
29.7.2_ce-160000.8.1

History

History
RecordedChangedSources
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2026-39984 is a medium vulnerability (CVSS 5.5) in Linuxfoundation Sigstore Timestamp Authority, published April 14, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.10%, the 0th percentile. Fixed in github.com/sigstore/timestamp-authority/v2 2.0.6.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 1,576 references and the rest of 2 source descriptions. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open