CVE-2026-48758: medium-severity vulnerability in sigstore-js
sigstore-js: DSSE payloadType type-binding failure
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.2%
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/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Affected products
sigstore · sigstore-jsRelated CVEs — sigstore-js
In the same product, most dangerous first.
CVE-2026-59891CRITICALCredential confusion in @sigstore/oci can leak registry credentials to an attacker-controlled registryEPSS 0.5%CVE-2026-118763HIGH@sigstore/oci sends the registry Authorization header to a cross-host blob-upload LocationEPSS 0.3%CVE-2026-48815HIGHsigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforcedEPSS 0.2%CVE-2026-48816MEDIUMsigstore-js: Insufficient Verification of Data AuthenticityEPSS 0.1%
References
https://github.com/sigstore/sigstore-js/commit/b5aa4f1f8d2db0a9dfa6430fb114d9c2f1c304f7https://github.com/sigstore/sigstore-js/pull/1657https://github.com/sigstore/sigstore-js/releases/tag/%40sigstore%2Fcore%403.2.1https://github.com/sigstore/sigstore-js/security/advisories/GHSA-jfc7-64v2-mr8c