source-map-js through 1.2.1 fails to validate the per-section offset line value in indexed source maps, allowing attackers to specify arbitrary numeric values. Attackers can supply extremely large offset line values that cause synchronous event loop blocking for extended periods, preventing the service from handling other requests.
CVE-2026-93749
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
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(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
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%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (4)
Auto-updated Sep 18, 2026source-map-js through 1.2.1 Event Loop Denial of Service | Advisories | VulnCheck
https://www.vulncheck.com/advisories/source-map-js-through-1.2.1-event-loop-denial-of-serviceSecurity Advisory: Event-loop denial of service in SourceNode via unvalidated section offset line · Issue #76 · 7rulnik/source-map-js · GitHub
https://github.com/7rulnik/source-map-js/issues/76source-map-js/lib/source-node.js at c1cd8904bb7bd0c7fb5879fcda48134d82a27934 · 7rulnik/source-map-js · GitHub
https://github.com/7rulnik/source-map-js/blob/c1cd8904bb7bd0c7fb5879fcda48134d82a27934/lib/source-node.js#L115-L118GitHub - 7rulnik/source-map-js: Consume and generate source maps. · GitHub
https://github.com/7rulnik/source-map-jsVendor Advisories for CVE-2026-93749(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-09-19 19:07 UTCEG score recompute
- 2026-09-19 19:07 UTCGHSA enrichment
- 2026-09-19 06:49 UTCEG score recompute
- 2026-09-19 06:48 UTCGHSA enrichment
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:54 UTCEG score recompute
- 2026-09-18 17:54 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-93749?
When was CVE-2026-93749 disclosed?
Is CVE-2026-93749 actively exploited?
What is the CVSS score of CVE-2026-93749?
How do I remediate CVE-2026-93749?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93749
Is Your Infrastructure Affected by CVE-2026-93749?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.