CVE-2026-49293

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.4%, top 67% 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.

js-toml is a TOML parser for JavaScript, fully compliant with the TOML 1.0.0 Spec. Versions up to and including 1.1.0 parse hexadecimal / octal / binary integer literals via a hand-written parseBigInt loop that multiplies a BigInt accumulator by the radix once per input digit. Each iteration performs a BigInt * BigInt operation on an accumulator that grows linearly with the number of digits already consumed, so the whole loop is O(n²) in the literal length. The lexer regex places no upper bound on the literal length, so a single TOML document containing one ~500 kB hex literal pins one CPU core for ~40 seconds on a modern laptop (Apple M-series, Node v22). Memory amplification is bounded but CPU amplification is severe and grows quadratically: doubling the literal length quadruples the work. A caller that invokes load() on attacker-controlled TOML (configuration upload endpoints, CI/CD systems ingesting third-party *.toml, IDE plugins, build tools) is exposed to a single-request CPU exhaustion DoS. Version 1.1.1 fixes the issue.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
33.4%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 26, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

CPU exhaustion via O(n^2) BigInt construction on radix-prefixed integer literals · Advisory · sunnyadn/js-toml · GitHub

https://github.com/sunnyadn/js-toml/security/advisories/GHSA-wp3c-266w-4qfq
github_release Patch Available

v1.1.1

Patch available: sunnyadn/js-toml v1.1.1

https://github.com/sunnyadn/js-toml/releases/tag/v1.1.1
github_commit Patch Available

commit 1abcb31dc7b1 (sunnyadn/js-toml)

Patch available: sunnyadn/js-toml v1.1.1 (contains commit 1abcb31dc7b1)

https://github.com/sunnyadn/js-toml/commit/1abcb31dc7b1fa88e4c848a8d108891cfbb96fa2

Vendor Advisories for CVE-2026-49293(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 46× 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-07-06 17:13 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 05:16 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 17:21 UTCEG score recompute
  6. 2026-07-05 05:26 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 16:53 UTCEG score recompute
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-04 04:34 UTCEG score recompute
  11. 2026-07-03 16:29 UTCEG score recompute
  12. 2026-07-03 04:33 UTCEG score recompute
  13. 2026-07-02 16:34 UTCEG score recompute
  14. 2026-07-02 04:38 UTCEG score recompute
  15. 2026-07-01 16:43 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 04:48 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 16:51 UTCEG score recompute
  20. 2026-06-30 04:57 UTCEG score recompute
  21. 2026-06-29 16:59 UTCEG score recompute
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 05:03 UTCEG score recompute
  25. 2026-06-28 17:07 UTCEG score recompute
Show 21 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 05:12 UTCEG score recompute
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 17:18 UTCEG score recompute
  6. 2026-06-27 05:23 UTCEG score recompute
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-26 17:28 UTCEG score recompute
  9. 2026-06-26 05:34 UTCEG score recompute
  10. 2026-06-25 17:39 UTCEG score recompute
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 05:44 UTCEG score recompute
  13. 2026-06-24 17:49 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-24 05:40 UTCEG score recompute
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-23 17:31 UTCEG score recompute
  19. 2026-06-23 05:37 UTCEG score recompute
  20. 2026-06-22 17:39 UTCEG score recompute
  21. 2026-06-22 17:37 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-49293?
CVE-2026-49293 is a high vulnerability published on June 19, 2026. js-toml is a TOML parser for JavaScript, fully compliant with the TOML 1.0.0 Spec. Versions up to and including 1.1.0 parse hexadecimal / octal / binary integer literals via a hand-written parseBigInt loop that multiplies a BigInt accumulator by the radix once per input digit. Each iteration…
When was CVE-2026-49293 disclosed?
CVE-2026-49293 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49293 actively exploited?
CVE-2026-49293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49293?
CVE-2026-49293 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-49293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49293, 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

Explore the affected products and dependency analysis for CVE-2026-49293

Explore →

Is Your Infrastructure Affected by CVE-2026-49293?

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

Start Free Scan →Browse All CVEs