CVE-2026-114142

waiting for further signalsZero needs more public information before it can validate it.

GHSA-h895-cgqg-jf52 ↗EUVD-2026-107553 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
BinaryMuse toml-node <= 5.0.0
fixed in >= 5.0.1
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
ETK-2026-2357Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/tome
2h 23msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h42m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

toml-node versions before 5.0.1 can allow untrusted TOML input to modify properties inherited through Object.prototype. An attacker who can cause an application to parse a crafted TOML document may influence the behavior of other objects in that process.

mitigation

Upgrade toml-node to version 5.0.1 or later. Until the upgrade is deployed, do not parse TOML from untrusted sources.

fixed in >= 5.0.1

check
no
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
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 20:28Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, 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:28Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2357",
  "cve_id": "CVE-2026-114142",
  "display_id": "CVE-2026-114142",
  "ghsa_id": "GHSA-h895-cgqg-jf52",
  "euvd_id": "EUVD-2026-107553",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Prototype pollution in toml-node TOML parsing",
  "summary": "toml-node versions before 5.0.1 can allow untrusted TOML input to modify properties inherited through Object.prototype. An attacker who can cause an application to parse a crafted TOML document may influence the behavior of other objects in that process.",
  "mitigation": "Upgrade toml-node to version 5.0.1 or later. Until the upgrade is deployed, do not parse TOML from untrusted sources.",
  "vendor": "BinaryMuse",
  "product": "toml-node",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 5.0.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        ">= 5.0.1"
      ],
      "package_name": "tome",
      "purl": "pkg:npm/tome"
    }
  ],
  "cwes": [
    1321
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.98909255,
  "t0_at": "2026-10-21T20:28:36.615000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T20:28:36.615000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:28:36.615000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114142"
    }
  }
}

published 2026-10-21 21:01Z
last change 2026-10-21 22:34Z

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.