CVE-2026-48815

HIGHPre-NVD 7.57.5
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
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
9%
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-gjxr
github_release Patch Available

[email protected]

Patch available: sigstore/sigstore-js [email protected]

https://github.com/sigstore/sigstore-js/releases/tag/sigstore%404.1.1
github_pr Patch Available

verification of OID certificate extensions

Patch available: sigstore/sigstore-js @sigstore/[email protected] (PR #1658 merged 2026-05-22)

https://github.com/sigstore/sigstore-js/pull/1658
github_commit Patch Available

commit 7845532f9d17 (sigstore/sigstore-js)

Patch available: sigstore/sigstore-js @sigstore/[email protected] (contains commit 7845532f9d17)

https://github.com/sigstore/sigstore-js/commit/7845532f9d17f6f765363dbee82b01bd159fb52b

Vendor 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)
PackageVulnerable rangeFixed inDependents
sigstore4.1.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 54× 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.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 16:17 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 23:23 UTCEG score recompute
  5. 2026-08-24 10:50 UTCEG score recompute
  6. 2026-08-23 08:26 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 06:59 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 05:48 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 04:37 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 20:57 UTCEG score recompute
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 23:20 UTCEG score recompute
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 19:47 UTCEG score recompute
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 07:06 UTCEG score recompute
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 06:01 UTCEG score recompute
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 04:43 UTCEG score recompute
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 46 more
  1. 2026-08-12 14:55 UTCEG score recompute
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-11 13:49 UTCEG score recompute
  4. 2026-08-11 01:16 UTCEG score recompute
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 00:10 UTCEG score recompute
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-08 23:04 UTCEG score recompute
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-07 21:57 UTCEG score recompute
  11. 2026-08-06 20:51 UTCEG score recompute
  12. 2026-08-06 13:47 UTCEPSS rescore
  13. 2026-08-05 19:45 UTCEG score recompute
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-04 16:40 UTCEG score recompute
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 15:34 UTCEG score recompute
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-02 14:28 UTCEG score recompute
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 13:21 UTCEG score recompute
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-30 23:37 UTCEG score recompute
  25. 2026-07-30 16:28 UTCEPSS rescore
  26. 2026-07-30 11:03 UTCEG score recompute
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-28 17:45 UTCEG score recompute
  29. 2026-07-28 15:37 UTCEPSS rescore
  30. 2026-07-27 15:59 UTCEG score recompute
  31. 2026-07-27 01:49 UTCEG score recompute
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 13:14 UTCEG score recompute
  34. 2026-07-24 14:18 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 03:18 UTCEG score recompute
  37. 2026-07-22 14:08 UTCEPSS rescore
  38. 2026-07-21 15:25 UTCEPSS rescore
  39. 2026-07-20 17:08 UTCEPSS rescore
  40. 2026-07-19 14:31 UTCEPSS rescore
  41. 2026-07-19 14:31 UTCEPSS rescore
  42. 2026-07-19 02:29 UTCEPSS rescore
  43. 2026-07-18 10:04 UTCEPSS rescore
  44. 2026-07-16 17:03 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-01 20:02 UTCEG score recompute

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 0% probability of exploitation in the next 30 days, which ranks it in the top 91.4% of all scored CVEs.
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

Explore →

Is Your Infrastructure Affected by CVE-2026-48815?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.