Vulnerability · Published Jul 14, 2026 · Assigned by GitHub_M

CVE-2026-48815sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced

High 7.5

In plain English

A high-severity security flaw in sigstore-js from sigstore. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High

Exploit odds (30 days)0.2%top 93.2% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	sigstore	4.1.1	GHSA-52v5-jr5w-gjxr

Affected products (as reported)

Vendor	Product	Versions
sigstore	sigstore-js	< 4.1.1

Weakness: CWE-347 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

References

https://github.com/sigstore/sigstore-js/security/advisories/GHSA-52v5-jr5w-gjxr x_refsource_CONFIRM
https://github.com/sigstore/sigstore-js/pull/1658 x_refsource_MISC
https://github.com/sigstore/sigstore-js/commit/7845532f9d17f6f765363dbee82b01bd159fb52b x_refsource_MISC
https://github.com/sigstore/sigstore-js/releases/tag/sigstore%404.1.1 x_refsource_MISC