Libexpat up to 2.10.0 Unicode xmltok.c DEFINE_UTF16_TO_UTF16 alternate encoding
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.20+ |
Summary
A vulnerability categorized as problematic has been discovered in Libexpat up to 2.10.0. This issue affects the function DEFINE_UTF16_TO_UTF16 of the file xmltok.c of the component Unicode Handler. Executing a manipulation can lead to improper handling of alternate encoding.
This vulnerability is tracked as CVE-2026-134703. The attack can be launched remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in Libexpat up to 2.10.0. This vulnerability affects the function DEFINE_UTF16_TO_UTF16 of the file xmltok.c of the component Unicode Handler. The manipulation with an unknown input leads to a improper handling of alternate encoding vulnerability. The CWE definition for the vulnerability is CWE-173. The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent. As an impact it is known to affect integrity. CVE summarizes:
libexpat through 2.10.0 contains an improper Unicode handling vulnerability in DEFINE_UTF16_TO_UTF16 conversion functions in xmltok.c that can split valid surrogate pairs when output space is limited. In XML_UNICODE builds parsing non-native byte order UTF-16 input, attackers can supply crafted documents that deliver lone high surrogates to character data and default handlers.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-134703 since 11/22/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/22/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper handling of alternate encodingCWE: CWE-173 / CWE-172
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/22/2026 Advisory disclosed11/22/2026 CVE reserved
11/22/2026 VulDB entry created
11/22/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CNA: VulnCheck
CVE: CVE-2026-134703 (🔒)
GCVE (CVE): GCVE-0-2026-134703
GCVE (VulDB): GCVE-100-442072
Entry
Created: 11/22/2026 03:40Changes: 11/22/2026 03:40 (75)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.