Skip to content
Applications

CVE-2026-76641

8.7
High
EPSS 0.35%Aug 22, 2026

Out-of-bounds read in Expat XML parser causing memory corruption or crash.

common questions

Is CVE-2026-76641 being exploited?

Not confirmed. CVE-2026-76641 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-76641?

CVE-2026-76641 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76641?

Not known from our data. No patch reference has been recorded for CVE-2026-76641, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-76641 affect?

CVE-2026-76641 affects Expat <= 2.8.3, Applications using XML_ExternalEntityParserCreate. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76641?

Apply vendor patch when released; disable external entity parsing and sanitize XML input.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Expat <= 2.8.3Applications using XML_ExternalEntityParserCreate
impact

Processing crafted XML with external-entity parsers can trigger out-of-bounds reads, leading to segfaults, memory corruption, and possible remote code execution in some contexts.

action required

Patch when possible

affected versions
libexpat libexpat
  • affected<= 2.8.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free