CVE-2025-66564

Sigstore Timestamp Authority allocates excessive memory during request parsing

Published Dec 4, 2025 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4qg8-fj49-pxjh Sigstore Timestamp Authority allocates excessive memory during request parsing
History
Type Values Removed Values Added
First Time appeared Linuxfoundation
Linuxfoundation sigstore Timestamp Authority
CPEs cpe:2.3:a:linuxfoundation:sigstore_timestamp_authority:*:*:*:*:*:*:*:*
Vendors & Products Linuxfoundation
Linuxfoundation sigstore Timestamp Authority
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Sigstore
Sigstore timestamp Authority
Vendors & Products Sigstore
Sigstore timestamp Authority
Type Values Removed Values Added
Description 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.
Title Sigstore Timestamp Authority allocates excessive memory during request parsing
Weaknesses CWE-405
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Dec 5, 2025, 2:55 PM
Reserved
Dec 4, 2025, 4:05 PM
Status
Analyzed
Published
Dec 4, 2025, 11:15 PM
Modified
Oct 18, 2026, 3:10 PM
Severity
Important
Public date
Dec 4, 2025, 10:37 PM