CVE-2026-85730

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-04 16:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-09 21:09 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 8.2 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-04 16:18 UTC

Last modified

2026-09-09 21:09 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-606

Record status

Deferred

Attack profile CVSS 4.0 · 8.2

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-85730.md and follow it. Check whether this project is affected by CVE-2026-85730. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge