CVE-2026-117610

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

GHSA-v4h5-6r69-76p3 ↗EUVD-2026-111545 ↗

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.
libexpat <= 2.9.0
CWE-476 NULL Pointer Dereference
ETK-2026-2823Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 25msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

libexpat through 2.9.0 can crash while parsing an external entity because of a NULL pointer dereference. An attacker must be able to influence XML stream chunking and trigger processing through an external entity subparser.

mitigation

Restrict untrusted XML processing, especially external entity handling, and do not allow untrusted parties to control incremental input chunking. Monitor for and deploy an upstream release newer than 2.9.0 when one is available.

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
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 02:03Z
Δ 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-10-28 02:03Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2823",
  "cve_id": "CVE-2026-117610",
  "display_id": "CVE-2026-117610",
  "ghsa_id": "GHSA-v4h5-6r69-76p3",
  "euvd_id": "EUVD-2026-111545",
  "status": "published",
  "anchor_state": "anchored",
  "title": "NULL pointer dereference in libexpat XML parsing",
  "summary": "libexpat through 2.9.0 can crash while parsing an external entity because of a NULL pointer dereference. An attacker must be able to influence XML stream chunking and trigger processing through an external entity subparser.",
  "mitigation": "Restrict untrusted XML processing, especially external entity handling, and do not allow untrusted parties to control incremental input chunking. Monitor for and deploy an upstream release newer than 2.9.0 when one is available.",
  "vendor": "libexpat",
  "product": "libexpat",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.9.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "libexpat",
      "purl": null
    }
  ],
  "cwes": [
    476
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/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": 14.502278533333333,
  "t0_at": "2026-10-28T02:03:18.766000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T02:03:18.766000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T02:03:18.766000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-117610"
    }
  }
}

published 2026-10-28 02:33Z
last change 2026-10-28 05:09Z

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.