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.
CVE-2026-48815
HIGHPre-NVD 7.57.5—Elevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 8.8%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available
`certificateOIDs` verification constraints are silently dropped and never enforced · Advisory · sigstore/sigstore-js · GitHub
https://github.com/sigstore/sigstore-js/security/advisories/GHSA-52v5-jr5w-gjxrgithub_release Patch Available
sigstore@4.1.1
Patch available: sigstore/sigstore-js sigstore@4.1.1
https://github.com/sigstore/sigstore-js/releases/tag/sigstore%404.1.1github_pr Patch Available
verification of OID certificate extensions
Patch available: sigstore/sigstore-js @sigstore/mock@0.12.1 (PR #1658 merged 2026-05-22)
https://github.com/sigstore/sigstore-js/pull/1658github_commit Patch Available
commit 7845532f9d17 (sigstore/sigstore-js)
Patch available: sigstore/sigstore-js @sigstore/mock@0.12.1 (contains commit 7845532f9d17)
https://github.com/sigstore/sigstore-js/commit/7845532f9d17f6f765363dbee82b01bd159fb52bVendor Advisories for CVE-2026-48815(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| sigstore | — | 4.1.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-01 20:02 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-48815?
CVE-2026-48815 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-48815 disclosed?
CVE-2026-48815 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48815 actively exploited?
CVE-2026-48815 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48815?
CVE-2026-48815 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48815?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48815, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48815
Is Your Infrastructure Affected by CVE-2026-48815?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.