CVE-2026-114143

validatedZero produced an exploit or a check.

GHSA-9j65-hcg3-gc64 ↗EUVD-2026-107555 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+20h07mkevAttacks confirmed in the real world.
npm:toml <= 5.0.0
fixed in 5.0.1
ETK-2026-2474Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/toml
+21h24mTTV
8mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+20h07mcheck available+21h24magent stopped
0
+6h
+12h
+18h

description

npm toml versions before 5.0.1 perform quadratic work when parsing TOML documents with very long dotted keys, table paths, or inline-table keys. An attacker able to supply TOML for parsing can block the Node.js event loop or cause the process to terminate through memory exhaustion. The maxDepth option does not limit dotted-key segment counts.

mitigation

Upgrade the npm toml package to version 5.0.1 or later. Until upgraded, reject untrusted TOML or enforce application-level limits on input size and dotted-key segment counts before parsing.

fixed in 5.0.1

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 20:31Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+20h07m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-21 20:31Z
    ghsa: trigger signal, started the run
  2. 2026-10-21 20:31Z
    public poc, published 2026-10-22 16:38Z
  3. 2026-10-21 20:31Z

this entry in the feed

GET /api/v1/feed/CVE-2026-114143

{
  "etk_id": "ETK-2026-2474",
  "cve_id": "CVE-2026-114143",
  "display_id": "CVE-2026-114143",
  "ghsa_id": "GHSA-9j65-hcg3-gc64",
  "euvd_id": "EUVD-2026-107555",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic parsing denial of service in npm toml",
  "summary": "npm `toml` versions before 5.0.1 perform quadratic work when parsing TOML documents with very long dotted keys, table paths, or inline-table keys. An attacker able to supply TOML for parsing can block the Node.js event loop or cause the process to terminate through memory exhaustion. The `maxDepth` option does not limit dotted-key segment counts.",
  "mitigation": "Upgrade the npm `toml` package to version 5.0.1 or later. Until upgraded, reject untrusted TOML or enforce application-level limits on input size and dotted-key segment counts before parsing.",
  "vendor": "npm",
  "product": "npm:toml",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 5.0.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "5.0.1"
      ],
      "package_name": "toml",
      "purl": "pkg:npm/toml"
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 8.49012465,
  "t0_at": "2026-10-21T20:31:01.539000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-22T17:55:10.773505+00:00",
      "days": 0.8917735475115741,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:31:01.539000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-22T16:38:06+00:00",
      "days": 0.8382460763888889,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:31:01.539000+00:00",
      "url": "https://github.com/advisories/GHSA-9j65-hcg3-gc64"
    },
    "trigger_signal": {
      "at": "2026-10-21T20:31:01.539000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:31:01.539000+00:00",
      "url": "https://github.com/advisories/GHSA-9j65-hcg3-gc64"
    }
  }
}

published 2026-10-22 17:46Z
last change 2026-10-22 18:24Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.