CVE-2026-48815
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.19%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 0.19% probability · 9th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-347
- Source
- security-advisories@github.com
References
- https://github.com/sigstore/sigstore-js/commit/7845532f9d17f6f765363dbee82b01bd159fb52b
- https://github.com/sigstore/sigstore-js/pull/1658
- https://github.com/sigstore/sigstore-js/releases/tag/sigstore%404.1.1
- https://github.com/sigstore/sigstore-js/security/advisories/GHSA-52v5-jr5w-gjxr
- https://github.com/sigstore/sigstore-js/security/advisories/GHSA-52v5-jr5w-gjxr
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.