CVE-2026-118370

libexpat through 2.9.0 Integer Overflow in storeAtts via attIndex and nPrefixes

Published Oct 28, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
libexpat through 2.9.0 contains a signed integer overflow vulnerability in storeAtts() in lib/xmlparse.c that allows attackers to trigger out-of-bounds writes via oversized attribute counts. Attackers can supply a multi-gigabyte document with a start tag carrying over 2^30 attributes to overflow attIndex and nPrefixes, crashing applications or corrupting heap memory.

Analysis

AI-generated

Technical impact

libexpat through 2.9.0 contains a signed integer overflow in the storeAtts() routine of lib/xmlparse.c. When an XML start tag carries an excessively large attribute count, the attIndex and nPrefixes counters wrap, allowing the function to write beyond the bounds of allocated memory. The description indicates an out‑of‑bounds write that can corrupt heap data. Based on the description, it is inferred that this corruption could cause application crashes or data corruption.

Affected Systems

All releases of libexpat up to and including version 2.9.0 are affected. Any application or service that integrates libexpat for XML parsing—such as web servers, XML‑handling utilities, or other software that processes XML—can be impacted. The CPE identifier indicates that libexpat is widely deployed across multiple platforms and operating systems.

Risk and Exploitability

The vulnerability has a CVSS score of 8.2, indicating high severity, while the EPSS score is less than 1% and it is not listed in the CISA KEV catalog, suggesting no widespread exploitation is currently documented. The description indicates that exploitation requires supplying an XML document with a start tag containing more than a billion attributes. Based on the description, it is inferred that this data may be delivered remotely or locally if the parsing endpoint accepts arbitrary data. Triggering the overflow can crash the host process, corrupt heap memory, and based on the description, it is inferred that it could lead to denial of service. No confirmed evidence of code execution or control‑flow hijacking exists based on the current documentation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update libexpat to a version that contains the integer overflow fix (e.g., the latest stable release beyond 2.9.0).
  • If no newer release is available, apply the upstream commit that corrects the storeAtts logic and rebuild the library.
  • Add input validation to reject XML documents whose start tags contain an impractically large number of attributes (e.g., limit to 1,000) to prevent the overflow from being triggered.

Generated by OpenCVE AI on November 5, 2026 at 02:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description libexpat through 2.9.0 contains a signed integer overflow vulnerability in storeAtts() in lib/xmlparse.c that allows attackers to trigger out-of-bounds writes via oversized attribute counts. Attackers can supply a multi-gigabyte document with a start tag carrying over 2^30 attributes to overflow attIndex and nPrefixes, crashing applications or corrupting heap memory.
Title libexpat through 2.9.0 Integer Overflow in storeAtts via attIndex and nPrefixes
First Time appeared Libexpat Project
Libexpat Project libexpat
Weaknesses CWE-190
CPEs cpe:2.3:a:libexpat_project:libexpat:*:*:*:*:*:*:*:*
Vendors & Products Libexpat Project
Libexpat Project libexpat
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 2, 2026, 7:56 PM
Reserved
Oct 28, 2026, 1:19 AM
Status
Analyzed
Published
Oct 28, 2026, 3:17 AM
Modified
Nov 2, 2026, 8:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 2:03 AM