CVE-2026-85730: smol-toml: Denial of Service via malformed TOML documents
Summary parse() can be forced into an infinite loop when a value inside an array or inline table is followed by a comment that has no trailing newline (i.e. the comment "ends" the document).
The library fails to exit an internal loop when attempting to find the end of the structure, resetting its cursor to the beginning of the string instead. This causes the parser to indefinitely hang, compromising the availability of the service.
Proof of concept
js import { parse } from 'smol-toml' parse('a=[1 #') // never returns; CPU pinned at 100%
Impact
Applications which parse arbitrary TOML documents can suffer major availability issues if they receive malicious input. This issue is particularly severe for these use-cases, and it is strongly advised to upgrade to an up-to-date version of the library as soon as possible.
If your use-case does not involve parsing arbitrary TOML documents from untrusted sources, the impact is much lower in practice, although it's still advisable to update to version 1.7.1.
Patches
Version 1.7.1 properly breaks out of the loop in these situations and throws the expected TomlError.
Workarounds
None that don't involve refactors. Update the library as soon as possible if your use-case involves parsing arbitrary TOML documents from untrusted sources.
Reported By : Ravindu Lakmina Munaweera
Other sources
smol-toml is a small, fast, and correct TOML parser and serializer. Prior to 1.7.1, parse() can enter an infinite loop when a value inside an array or inline table is followed by a comment with no trailing newline. In src/util.ts, skipUntil() calls indexOfNewline(), receives -1 at the end of input, and resets the cursor to the beginning of the string instead of leaving the structure scan. The parser then hangs indefinitely and can consume a service's processing capacity when an application parses attacker-controlled TOML. This issue is fixed in version 1.7.1.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/smol-tomlto a version that resolves this vulnerability.Fixed in 1.7.1 - Upgrade
Upgrade
smol-tomlto a version that resolves this vulnerability.Fixed in 1.7.1
Event History
Frequently Asked Questions
Which deployments are exposed to this denial-of-service condition?
Applications using smol-toml versions prior to 1.7.1 are exposed when they parse attacker-controlled TOML input. A crafted document can cause parsing to hang and consume processing capacity.
What input is required to trigger the issue?
The TOML must contain a value inside an array or inline table followed by a comment that has no trailing newline at the end of the input.
What is the remediation?
Upgrade smol-toml to version 1.7.1, which fixes the parser behavior.