Every CVE Search/ Get API key

CVE-2025-66564

Sigstore Timestamp Authority allocates excessive memory during request parsing

7.5 HighFix available

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
None
Availability
High

Exploit likelihood

0.47%Up 0.4 points since Dec 5, 2025
90%50%10%1%

What each source reports

CVE List Score used 7.5

Sigstore Timestamp Authority allocates excessive memory during request parsing

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Record
CVE-2025-66564
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-405
Updated
2026-11-02
EUVDEUVD-2025-201319 7.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Record
EUVD-2025-201319
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-4qg8-fj49-pxjh 7.5

Sigstore Timestamp Authority allocates excessive memory during request parsing

Impact

Excessive memory allocation

Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string.

As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Patches

Upgrade to v2.0.3.

Workarounds

There are no workarounds with the service itself. If the service is behind a load balancer, configure the load balancer to reject excessively large requests.

Record
GHSA-4qg8-fj49-pxjh
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-405
Updated
2026-11-02
NVD 7.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Record
CVE-2025-66564
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-405
Updated
2026-11-02
OSV 7.5

Sigstore Timestamp Authority allocates excessive memory during request parsing

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Record
CVE-2025-66564
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-405
Updated
2026-11-02
OSVDEBIAN-CVE-2025-66564 7.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Record
DEBIAN-CVE-2025-66564
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Updated
2026-11-02
Show 7 moreShow less
OSVGHSA-4qg8-fj49-pxjh 7.5

Sigstore Timestamp Authority allocates excessive memory during request parsing

Impact

Excessive memory allocation

Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string.

As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Patches

Upgrade to v2.0.3.

Workarounds

There are no workarounds with the service itself. If the service is behind a load balancer, configure the load balancer to reject excessively large requests.

Record
GHSA-4qg8-fj49-pxjh
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-405
Updated
2026-11-02
OSVUBUNTU-CVE-2025-66564 7.5

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.

Record
UBUNTU-CVE-2025-66564
CVSS 3.1
7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Updated
2026-11-02
OSVGO-2025-4192 No score

Sigstore Timestamp Authority allocates excessive memory during request parsing in github.com/sigstore/timestamp-authority

Sigstore Timestamp Authority allocates excessive memory during request parsing in github.com/sigstore/timestamp-authority

Record
GO-2025-4192
Updated
2026-11-02
OSVopenSUSE-SU-2026:10131-1 No score

trivy-0.69.0-1.1 on GA media

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

Record
openSUSE-SU-2026:10131-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:20191-1 No score

Security update for trivy

This update for trivy fixes the following issues:

Changes in trivy:

  • Update to version 0.69.0 (bsc#1255366, CVE-2025-64702):
    • release: v0.69.0 [main] (#9886)
    • chore: bump trivy-checks to v2 (#9875)
    • chore(deps): bump github.com/theupdateframework/go-tuf/v2 from 2.3.1 to 2.4.1 (#10091)
    • fix(repo): return a nil interface for gitAuth if missing (#10097)
    • fix(java): correctly inherit properties from parent fields for pom.xml files (#9111)
    • fix(rust): implement version inheritance for Cargo mono repos (#10011)
    • feat(activestate): add support ActiveState images (#10081)
    • feat(vex): support per-repo tls configuration (#10030)
    • refactor: allow per-request transport options override (#10083)
    • chore(deps): bump github.com/sigstore/rekor from 1.4.3 to 1.5.0 (#10084)
    • chore(deps): bump github.com/sigstore/sigstore from 1.10.3 to 1.10.4 (#10085)
    • fix(java): correctly propagate repositories from upper POMs to dependencies (#10077)
    • feat(rocky): enable modular package vulnerability detection (#10069)
    • chore(deps): bump github.com/theupdateframework/go-tuf/v2 from 2.3.0 to 2.3.1 (#10079)
    • docs: fix mistake in config file example for skip-dirs/skip-files flag (#10070)
    • feat(report): add Trivy version to JSON output (#10065)
    • fix(rust): add cargo workspace members glob support (#10032)
    • feat: add AnalyzedBy field to track which analyzer detected packages (#10059)
    • fix: use canonical SPDX license IDs from embeded licenses.json (#10053)
    • docs: fix link to Docker Image Specification (#10057)
    • feat(secret): add detection for Symfony default secret key (#9892)
    • refactor(misconf): move common logic to base value and simplify typed values (#9986)
    • fix(java): add hash of GAV+root pom file path for pkgID for packages from pom.xml files (#9880)
    • feat(misconf): use Terraform plan configuration to partially restore schema (#9623)
    • feat(misconf): add action block to Terraform schema (#10035)
    • fix(misconf): correct typos in block and attribute names (#9993)
    • test(misconf): simplify test values using *Test helpers (#9985)
    • fix(misconf): safely parse rotation_period in google_kms_crypto_key (#9980)
    • feat(misconf): support for ARM resources defined as an object (#9959)
    • feat(misconf): support for azurerm_*_web_app (#9944)
    • test: migrate private test helpers to export_test.go convention (#10043)
    • chore(deps): bump github.com/sigstore/cosign/v2 from 2.2.4 to 2.6.2 (#10048)
    • fix(secret): improve word boundary detection for Hugging Face tokens (#10046)
    • fix(go): use ldflags version for all pseudo-versions (#10037)
    • chore: switch to ID from AVDID in internal and user-facing fields (#9655)
    • refactor(misconf)!: use ID instead of AVDID for providers mapping (#9752)
    • fix: move enum into items for array-type fields in JSON Schema (#10039)
    • docs: fix incorrect documentation URLs (#10038)
    • feat(sbom): exclude PEP 770 SBOMs in .dist-info/sboms/ (#10033)
    • fix(docker): fix non-det scan results for images with embedded SBOM (#9866)
    • chore(deps): bump the github-actions group with 11 updates (#10001)
    • test: fix assertion after 2026 roll over (#10002)
    • fix(vuln): skip vulns detection for CentOS Stream family without scan failure (#9964)
    • fix(license): normalize licenses for PostAnalyzers (#9941)
    • feat(nodejs): parse licenses from package-lock.json file (#9983)
    • chore: update reference links to Go Wiki (#9987)
    • refactor: add xslices.Map and replace lo.Map usages (#9984)
    • fix(image): race condition in image artifact inspection (#9966)
    • feat(flag): add JSON Schema for trivy.yaml configuration file (#9971)
    • refactor(debian): use txtar format for test data (#9957)
    • chore(deps): bump golang.org/x/tools to v0.40.0 + gopls to v0.21.0 (#9973)
    • feat(rootio): Update trivy db to support usage of Severity from root.io feed (#9930)
    • feat(vuln): skip vulnerability scanning for third-party packages in Debian/Ubuntu…
Record
openSUSE-SU-2026:20191-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
OSVSUSE-SU-2025:4395-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20251209T172047 2025-12-09T17:20:47Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-4006 CVE-2025-61725
    • GO-2025-4176 CVE-2025-65105 GHSA-j3rw-fx6g-q46j
    • GO-2025-4177 CVE-2025-64750 GHSA-wwrx-w7c9-rf87
    • GO-2025-4178 CVE-2025-13870 GHSA-58w6-w55x-6wq8
    • GO-2025-4179 CVE-2025-64443 GHSA-46gc-mwh4-cc5r
    • GO-2025-4180 CVE-2025-44005 GHSA-h8cp-697h-8c8p
    • GO-2025-4181 CVE-2025-66406 GHSA-j7c9-79x7-8hpr
    • GO-2025-4182 CVE-2025-66411 GHSA-jf75-p25m-pw74
    • GO-2025-4183 CVE-2017-18870 GHSA-9j9j-mm2r-9rfm
    • GO-2025-4184 CVE-2017-18871 GHSA-jc6w-8r7f-vmp5
    • GO-2025-4185 CVE-2017-18902 GHSA-jwfv-5hwq-f97r
    • GO-2025-4186 CVE-2017-18875 GHSA-9rr5-q43r-ccv4
    • GO-2025-4187 CVE-2017-18876 GHSA-hjqh-j6rj-gh8q
    • GO-2025-4189 CVE-2017-18879 GHSA-498j-wxww-j897
    • GO-2025-4190 CVE-2017-18877 GHSA-9x8x-w6g5-hx4w
    • GO-2025-4192 CVE-2025-66564 GHSA-4qg8-fj49-pxjh
    • GO-2025-4193 CVE-2025-66506 GHSA-f83f-xpx7-ffpw
    • GO-2025-4197 CVE-2017-18884 GHSA-876j-jfqf-m7j7
    • GO-2025-4198 CVE-2017-18883 GHSA-w8cc-3h7q-jhc3

  • Update to version 0.0.20251203T174324 2025-12-03T17:43:24Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-4155 CVE-2025-61729
    • GO-2025-4163 CVE-2025-60638 GHSA-f2hj-vpp9-6vm2
    • GO-2025-4164 CVE-2025-60632 GHSA-vgq7-9r5r-j9v3
    • GO-2025-4171 CVE-2025-66410 GHSA-jrhg-82w2-vvj7
    • GO-2025-4172 CVE-2025-12756 GHSA-p6gj-jc38-x2m7
    • GO-2025-4174 CVE-2025-13353 GHSA-69jw-4jj8-fcxm
    • GO-2025-4175 CVE-2025-61727

  • Update to version 0.0.20251125T181218 2025-11-25T18:12:18Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-4133 CVE-2025-55074 GHSA-9hh7-6558-qfp2
    • GO-2025-4138 CVE-2025-65025 GHSA-h3mw-4f23-gwpw
    • GO-2025-4139 CVE-2025-65026 GHSA-hcpf-qv9m-vfgp
    • GO-2025-4146 CVE-2018-21258 GHSA-5mh6-p63g-3mv5
    • GO-2025-4147 GHSA-6xvf-4vh9-mw47
    • GO-2025-4149 CVE-2025-13425 GHSA-f786-75f3-74xj
    • GO-2025-4150 CVE-2025-64751 GHSA-2c64-vmv2-hgfc
    • GO-2025-4151 CVE-2025-65111 GHSA-9m7r-g8hg-x3vr
    • GO-2025-4152 CVE-2025-13357 GHSA-gmm6-j2g5-r52m
    • GO-2025-4153 CVE-2025-41115 GHSA-w62r-7c53-fmc5
    • GO-2025-4156 CVE-2025-64761 GHSA-7ff4-jw48-3436
    • GO-2025-4157 GHSA-2fcv-qww3-9v6h
    • GO-2025-4158 GHSA-rj4j-2jph-gg43
    • GO-2025-4159 GHSA-xq4h-wqm2-668w
    • GO-2025-4160 CVE-2025-65965 GHSA-6gxw-85q2-q646
Record
SUSE-SU-2025:4395-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/sigstore/timestamp-authority
Go
 through 2.0.2
2.0.3
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.0.3-1, plus listed versions
1.2.3-21.2.9-1
2.0.3-1
github.com/sigstore/timestamp-authority
Go
 before 2.0.3
2.0.3
github.com/sigstore/timestamp-authority
Go
 All versions None known
github.com/sigstore/timestamp-authority/v2
Go
 before 2.0.3
2.0.3
govulncheck-vulndb
SUSE:Linux Enterprise Module for Package Hub 15 SP6
From an advisory covering 37 CVEs
 before 0.0.20251209T172047-150000.1.127.1
0.0.20251209T172047-150000.1.127.1
govulncheck-vulndb
openSUSE:Leap 15.6
From an advisory covering 37 CVEs
 before 0.0.20251209T172047-150000.1.127.1
0.0.20251209T172047-150000.1.127.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
From an advisory covering 2 CVEs
 before 0.69.0-1.1
0.69.0-1.1
govulncheck-vulndb
openSUSE:Leap 16.0
From an advisory covering 1734 CVEs
 before 0.0.20260723T184607-160000.1.1
0.0.20260723T184607-160000.1.1

History

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

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

In short

CVE-2025-66564 is a high vulnerability (CVSS 7.5) in Linuxfoundation Sigstore Timestamp Authority, published December 4, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.47%, the 41st percentile. Fixed in github.com/sigstore/timestamp-authority 2.0.3.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 1,545 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