Skip to main content
VulnerabilityPublished

CVE-2026-134703: libexpat · Improper Handling of Unicode Encoding

Affects libexpatSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 22 Nov 2026, 02:24 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 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 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
libexpatlibexpatAffected
  • <=2.10.0
Fixed in–
GitHublibexpatpkg:github/libexpatOther threatsAffected
  • <=2.10.0
Fixed in–

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

AI-suggested

Until a fix is available, users should consider avoiding XML_UNICODE builds parsing non-native byte order UTF-16 input or apply any vendor-recommended mitigations once published.

Description

CVE-2026-134703 is a vulnerability in libexpat up to version 2.10.0 involving improper handling of Unicode encoding in the DEFINE_UTF16_TO_UTF16 conversion functions. This flaw can cause valid surrogate pairs to be split when output space is limited, specifically in XML_UNICODE builds parsing non-native byte order UTF-16 input. Crafted XML documents can deliver lone high surrogates to character data and default handlers, potentially leading to parsing issues.

References

Community reviews

Loading reviews…