Skip to main content
CVE-2026-63386VulnerabilityPublished

Js-toml Allows Uncontrolled Recursion

Affects js-tomlSource GCVE Database

0
Compare
Authoritative record:CVE-2026-63386· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.1.3 when convenient.

Data as of 20 Nov 2026, 15:55 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.1.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade js-toml to 1.1.3.

Affected software

ProductAffectedFixed in
npmjs-tomlAffected
  • <1.1.3
Fixed in
  • 1.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in js-toml version 1.1.3. Users should upgrade to version 1.1.3 or later. The fix enforces a configurable maximum nesting/key depth limit and converts stack overflow RangeErrors into SyntaxParseErrors, preserving the documented error contract. Until upgraded, applications should catch all exceptions from load() to prevent process crashes.

Description

The js-toml library's load() function parses TOML input using recursive parsing and interpretation without enforcing a maximum nesting depth. Deeply nested arrays, inline tables, or dotted keys cause recursion to exceed the V8 JavaScript engine's call stack limit, triggering an uncaught RangeError. This error differs from the expected SyntaxParseError, breaking error handling contracts and potentially crashing Node.js processes if unhandled. The issue affects versions prior to 1.1.3 and is fixed in 1.1.3.

References

Community reviews

Loading reviews…