CVE-2026-48815: high-severity vulnerability in sigstore-js
sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.2%
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 4.1.1, the documented certificateOIDs option in sigstore.verify() is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked and applications relying on certificateOIDs to restrict which certificates may sign artifacts can accept unauthorized certificates. This issue is fixed in version 4.1.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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-48758MEDIUMsigstore-js: DSSE payloadType type-binding failureEPSS 0.2%CVE-2026-48816MEDIUMsigstore-js: Insufficient Verification of Data AuthenticityEPSS 0.1%