CVE-2026-48815
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
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - EPSS
- 0.2% chance of exploitation in the next 30 days; higher than 6% of CVEs (scores of 2026-10-25)
- CWE
- CWE-347
- Published
- Modified
- Record from
- the NVD, synced
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-52v5-jr5w-gjxr | npm | sigstore | <4.1.1 | 4.1.1 |
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