CVE-2026-77214

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

GHSA-8xfx-9m5m-pgcp ↗EUVD-2026-94368 ↗

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.8.5
CWE-125 Out-of-bounds Read
ETK-2026-882, permanent identifier
14d 02h 42msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

libexpat revisions before commit 13c5f63 can read beyond an allocated parse buffer when applications use XML_ParseBuffer. An attacker may cause adjacent process memory to be exposed through the calling application when a parse buffer has already been established.

mitigation

Update libexpat to a revision containing commit 13c5f63 or later. Until then, avoid using XML_ParseBuffer with attacker-influenced lengths, and ensure supplied lengths cannot exceed the allocated parse buffer.

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.
–
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.
0.55%44th percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 14:35Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-07 14:35Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-882",
  "cve_id": "CVE-2026-77214",
  "display_id": "CVE-2026-77214",
  "ghsa_id": "GHSA-8xfx-9m5m-pgcp",
  "euvd_id": "EUVD-2026-94368",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap buffer over-read in libexpat XML parsing",
  "summary": "libexpat revisions before commit 13c5f63 can read beyond an allocated parse buffer when applications use XML_ParseBuffer. An attacker may cause adjacent process memory to be exposed through the calling application when a parse buffer has already been established.",
  "mitigation": "Update libexpat to a revision containing commit 13c5f63 or later. Until then, avoid using XML_ParseBuffer with attacker-influenced lengths, and ensure supplied lengths cannot exceed the allocated parse buffer.",
  "vendor": "libexpat",
  "product": "libexpat",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.8.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "libexpat",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N",
  "epss_score": 0.0055,
  "epss_percentile": 0.4488,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.918844633333332,
  "t0_at": "2026-10-07T14:35:42.794000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T14:35:42.794000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T14:35:42.794000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-77214"
    }
  }
}

published 2026-10-07 14:58Z
last change 2026-10-21 05:31Z

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.