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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-1333",
"CWE-400",
"CWE-407"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/49xxx/CVE-2026-49293.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:sunnyadn:js-toml:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.1.1"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "1abcb31dc7b1fa88e4c848a8d108891cfbb96fa2"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v1.1.1",
"range": [
{
"fixed": "60d0741b59f8ae0699c0e0f04ca004f04302bcac"
}
],
"source": "REFERENCES_TAG"
}
]
}