Advisory

GHSA-v3rj-xjv7-4jmq

Also known as: None

Summary

smol-toml: Denial of Service via TOML documents containing thousands of consecutive commented lines

Details

Summary
An attacker can send a maliciously crafted TOML to cause the parser to crash, because of a stack overflow caused by thousands of consecutive commented lines.

The library uses recursion internally while parsing to skip over commented lines, which can be exploited to crash an application that is processing arbitrary TOML documents.

Proof of concept

require("smol-toml").parse('# comment\n'.repeat(8000) + 'key = "value"')

Impact
Applications which parse arbitrary TOML documents may suffer availability issues if they receive malicious input. If uncaught, the crash may cause the application itself to crash. The impact is deemed minor, as the function is already likely to throw errors on invalid input. Downstream users are supposed to properly handle errors in such situations.

Due to the design of most JavaScript runtimes, the uncontrolled recursion does not lead to excessive memory usage and the execution is quickly aborted.

As a reminder, it is strongly advised when working with untrusted user input to expect errors to occur and to appropriately catch them.

Patches
Version 1.6.1 uses a different approach for parsing comments, which no longer involves recursion.

Workarounds
Wrap all invocations of parse and stringify in a try/catch block when dealing with untrusted user input.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-25 21:03 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

smol-toml

npm · All systems

Affected

  • introduced 0, fixed 1.6.1 (semver)

Fixed versions

1.6.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences