Skip to main content

js-toml CVE-2026-49293

| EUVDEUVD-2026-38060 HIGH
Uncontrolled Resource Consumption (CWE-400)
2026-06-19 GitHub_M GHSA-wp3c-266w-4qfq
7.5
CVSS 3.1 · Vendor: GitHub_M
Share

Severity by source

Vendor (GitHub_M) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
7.5 HIGH

Single attacker-controlled TOML document parsed by an unauthenticated network-reachable caller (AV:N/AC:L/PR:N/UI:N) causes CPU exhaustion only (C:N/I:N/A:H).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Patch available
Jun 19, 2026 - 21:02 EUVD
Source Code Evidence Fetched
Jun 19, 2026 - 19:01 vuln.today
Analysis Generated
Jun 19, 2026 - 19:01 vuln.today
CVE Published
Jun 19, 2026 - 18:14 cve.org
HIGH 7.5

DescriptionCVE.org

js-toml is a TOML parser for JavaScript, fully compliant with the TOML 1.0.0 Spec. Versions up to and including 1.1.0 parse hexadecimal / octal / binary integer literals via a hand-written parseBigInt loop that multiplies a BigInt accumulator by the radix once per input digit. Each iteration performs a BigInt * BigInt operation on an accumulator that grows linearly with the number of digits already consumed, so the whole loop is O(n²) in the literal length. The lexer regex places no upper bound on the literal length, so a single TOML document containing one ~500 kB hex literal pins one CPU core for ~40 seconds on a modern laptop (Apple M-series, Node v22). Memory amplification is bounded but CPU amplification is severe and grows quadratically: doubling the literal length quadruples the work. A caller that invokes load() on attacker-controlled TOML (configuration upload endpoints, CI/CD systems ingesting third-party *.toml, IDE plugins, build tools) is exposed to a single-request CPU exhaustion DoS. Version 1.1.1 fixes the issue.

AnalysisAI

Denial of service in js-toml versions up to and including 1.1.0 allows remote attackers to exhaust CPU resources by submitting a single TOML document containing an oversized hexadecimal, octal, or binary integer literal. The hand-written parseBigInt loop exhibits O(n²) complexity, and a ~500 kB literal pins one CPU core for ~40 seconds; no public exploit identified at time of analysis, but the patched commit and test suite serve as a clear blueprint. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Recon
Identify TOML ingestion endpoint
Delivery
Craft document with ~500KB hex literal
Exploit
Submit via HTTP/CI/upload
Install
Trigger O(n²) parseBigInt loop
C2
Pin Node.js event loop ~40s
Execute
Repeat to exhaust workers
Impact
Service-wide denial of service

Vulnerability AssessmentAI

Exploitation The target application must call js-toml's `load()` function on attacker-influenced TOML input - typical exposures are HTTP endpoints that accept TOML configuration uploads, CI/CD systems ingesting third-party `*.toml` from repositories or artifacts, IDE plugins parsing project files, and build tools consuming dependency manifests. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5 High) accurately reflects a network-reachable, unauthenticated, single-request availability-only impact in deployments that feed untrusted TOML into js-toml. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker submits a single TOML configuration file (e.g. via a SaaS configuration upload endpoint, webhook, or CI/CD job processing an untrusted repository's `*.toml`) containing a payload like `x = 0x` followed by ~500,000 hex characters. …
Remediation Vendor-released patch: upgrade js-toml to 1.1.1 or later (https://github.com/sunnyadn/js-toml/releases/tag/v1.1.1), which introduces a 1000-digit cap on radix-prefixed integer literals and replaces the quadratic parseBigInt loop with the native BigInt constructor (commit 1abcb31dc7b1fa88e4c848a8d108891cfbb96fa2). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Inventory all js-toml usage across applications and CI/CD infrastructure; assess exposure level for each instance. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-49293 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy