CVE-2026-48758
Prior to 3.2.1, the preAuthEncoding function in @sigstore/core uses Node.js ascii encoding when converting the PAE string to bytes, allowing payloadType to be mutated after signing without invalidating the signature and breaking the type-binding…
Does this matter?
Lower severity and a low EPSS score (0.26%). Track it; it rarely justifies an emergency change on its own.
Description
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.2.1, the preAuthEncoding function in @sigstore/core uses Node.js ascii encoding when converting the PAE string to bytes, allowing payloadType to be mutated after signing without invalidating the signature and breaking the type-binding guarantee that DSSE is designed to provide. This issue is fixed in version 3.2.1.
- CVSS 3.1
- 5.4 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- EPSS
- 0.26% probability · 18th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-347
- Source
- security-advisories@github.com
References
- https://github.com/sigstore/sigstore-js/commit/b5aa4f1f8d2db0a9dfa6430fb114d9c2f1c304f7
- https://github.com/sigstore/sigstore-js/pull/1657
- https://github.com/sigstore/sigstore-js/releases/tag/%40sigstore%2Fcore%403.2.1
- https://github.com/sigstore/sigstore-js/security/advisories/GHSA-jfc7-64v2-mr8c
- https://github.com/sigstore/sigstore-js/security/advisories/GHSA-jfc7-64v2-mr8c
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.