Sigstore Timestamp Authority allocates excessive memory during request parsing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2025-66564: 0.44% estimated exploitation activity in the next 30 days; percentile 38.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

5 Dec 2025, 18:19 UTC

Last modified by the source

5 Dec 2025, 18:19 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4qg8-fj49-pxjh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-66564

Advisory: Sigstore Timestamp Authority allocates excessive memory during request parsing
IDs: CVE-2025-66564, GHSA-4qg8-fj49-pxjh
Record: https://patchnext.com/advisories/cve-2025-66564 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/sigstore/timestamp-authority 2.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/sigstore/timestamp-authority: affected <= 2.0.2; fixed in 2.0.3

## Suggested inspection (read-only)
- Go github.com/sigstore/timestamp-authority: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/sigstore/timestamp-authority.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4qg8-fj49-pxjh (GitHub-reviewed advisory GHSA-4qg8-fj49-pxjh lists affected ranges: Go github.com/sigstore/timestamp-authority >=0 <=2.0.2)

Commands are suggestions: review each one before running it.