Asymmetric Resource Consumption (Amplification) Affecting golang-github-sigstore-timestamp-authority package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN14-GOLANGGITHUBSIGSTORETIMESTAMPAUTHORITY-14193189
- published6 Dec 2025
- disclosed4 Dec 2025
Introduced: 4 Dec 2025
NewCVE-2025-66564 (opens in a new tab)How to fix?
There is no fixed version for Debian:14 golang-github-sigstore-timestamp-authority.
NVD Description
Note: Versions mentioned in the description apply only to the upstream golang-github-sigstore-timestamp-authority package and not the golang-github-sigstore-timestamp-authority package as distributed by Debian.
See How to fix? for Debian:14 relevant fixed versions and status.
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.