CVE-2026-124078

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

GHSA-rwwr-mcmf-whxp ↗EUVD-2026-118495 ↗

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.
TooTallNate plist.js < 5.0.1
fixed in 5.0.1
CWE-776 Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
ETK-2026-3760Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/plist.js
1d 03h 30msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h33m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

plist.js before 5.0.1 is affected when an application parses attacker-controlled binary property-list data. An unauthenticated attacker can cause excessive resource use and crash the Node.js process, resulting in denial of service.

mitigation

Upgrade the npm plist package to version 5.0.1 or later. Restrict untrusted binary plist input until the update is deployed.

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
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 20:51Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-06 20:51Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3760",
  "cve_id": "CVE-2026-124078",
  "display_id": "CVE-2026-124078",
  "ghsa_id": "GHSA-rwwr-mcmf-whxp",
  "euvd_id": "EUVD-2026-118495",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in plist.js binary plist parser",
  "summary": "plist.js before 5.0.1 is affected when an application parses attacker-controlled binary property-list data. An unauthenticated attacker can cause excessive resource use and crash the Node.js process, resulting in denial of service.",
  "mitigation": "Upgrade the npm plist package to version 5.0.1 or later. Restrict untrusted binary plist input until the update is deployed.",
  "vendor": "TooTallNate",
  "product": "plist.js",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.0.1"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "5.0.1"
      ],
      "package_name": "plist.js",
      "purl": "pkg:npm/plist.js"
    }
  ],
  "cwes": [
    776
  ],
  "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": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.212839616666667,
  "t0_at": "2026-11-06T20:51:17.545000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T20:51:17.545000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T20:51:17.545000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-124078"
    }
  }
}

published 2026-11-06 21:13Z
last change 2026-11-07 11:22Z

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.