GHSA-wp3c-266w-4qfq: js-toml (CVE-2026-49293)

Package	Ecosystem	Affected	Fixed in
js-toml	npm	<1.1.2	1.1.2

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

js-toml before 1.1.2 parses hexadecimal, octal and binary integer literals with a quadratic-time routine. An attacker who supplies a TOML document with a very long such literal to load() can exhaust CPU and stall the process. Upgrade to js-toml 1.1.2 or later; until then, limit the size of untrusted TOML input.

Written 15 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
7.5	High	3.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H	CNA (GitHub_M)

CISA KEV Not listed.
EPSS 0.0064, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

19 Jun 2026, 18:14 UTC Confirmed by the CVE List
19 Jun 2026, 19:16 UTC Confirmed by NVD
26 Jun 2026, 22:21 UTC Confirmed by GitHub Advisory Database
4 Nov 2026, 03:45 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.