Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

smol-toml: Denial of Service via malformed TOML documents

CVE-2026-85730GHSA-7w5x-hrqm-74c2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (smol-toml 1.7.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-85730: 0.52% estimated exploitation activity in the next 30 days; percentile 44.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-7w5x-hrqm-74c2

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-7w5x-hrqm-74c2

  4. Revision 1 · created ·

    Published from ghsa record GHSA-7w5x-hrqm-74c2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-85730

Advisory: smol-toml: Denial of Service via malformed TOML documents
IDs: CVE-2026-85730, GHSA-7w5x-hrqm-74c2
Record: https://patchnext.com/advisories/cve-2026-85730 (revision 4, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: smol-toml 1.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm smol-toml: affected <= 1.7.0; fixed in 1.7.1

## Suggested inspection (read-only)
- `npm ls smol-toml --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on smol-toml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7w5x-hrqm-74c2 (GitHub-reviewed advisory GHSA-7w5x-hrqm-74c2 lists affected ranges: npm smol-toml >=0 <=1.7.0)
- Verified: https://osv.dev/vulnerability/GHSA-7w5x-hrqm-74c2 (OSV record GHSA-7w5x-hrqm-74c2 lists affected ranges: npm smol-toml >=0 <1.7.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…