CVE-2026-85730

### 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](https://www.linkedin.com/in/ravindulakmina/)