Skip to main content
VulnerabilityPublished Updated

CVE-2026-76957: libexpat · Use After Free

Affects libexpatSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 4.9 Medium : upgrade to 2.8.4 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mitre)CVSS 3.14.9
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.8.4
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade libexpat and libexpat/libexpat to 2.8.4.

Affected software

ProductAffectedFixed in
libexpat projectlibexpatAffected
  • <2.8.4
Fixed in
  • 2.8.4
GitHublibexpat/libexpatpkg:github/libexpat/libexpatOther threatsAffected
  • <2.8.4
Fixed in
  • 2.8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability is available in libexpat version 2.8.4. Users and maintainers should upgrade to version 2.8.4 or later to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-76957 is a use-after-free vulnerability in libexpat versions before 2.8.4. It arises due to the lack of handler call depth tracking when using custom encoding callbacks. This flaw can lead to memory corruption issues similar to other CVEs in the libexpat project. The vulnerability has a medium severity rating and is fixed in version 2.8.4.

References

Community reviews

Loading reviews…