CVE-2026-49293: high-severity vulnerability in sunnyadn js-toml
CPU exhaustion via O(n^2) BigInt construction on radix-prefixed integer literals
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.6%
js-toml is a TOML parser for JavaScript, fully compliant with the TOML 1.0.0 Spec. Versions up to and including 1.1.1 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.2 fixes the issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
sunnyadn · js-tomlRelated CVEs — sunnyadn js-toml
In the same product, most dangerous first.
CVE-2025-54803HIGHjs-toml is vulnerable to Prototype PollutionEPSS 0.6%CVE-2026-50029MEDIUMjs-toml has silent type confusion via falsy-primitive duplicate-key bypassEPSS 0.4%CVE-2026-63386MEDIUMjs-toml: Uncontrolled recursion in `load()` causes `RangeError` (stack exhaustion) on deeply nested inputEPSS 0.4%