High · CVSS 8.2CVE-2026-113351

libexpat 2.7.2 through 2.9.0 Denial of Service via XML_ParserResetCVE-2026-113351

Answer in brief

CVE-2026-113351 records a High severity (CVSS 8.2) vulnerability in libexpat 2.7.2 through 2.9.0 Denial of Service via XML_ParserReset. The current sources do not mark it as known exploited. The current feed maps libexpat/libexpat (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 20, 2026Updated Oct 20, 2026Source checked Oct 20, 2026First seen by HOL Oct 20, 2026Material review Oct 20, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.2
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps libexpat/libexpat (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
libexpat/libexpatgeneric	>=2.7.2 <=2.9.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for libexpat/libexpat.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 20, 2026

Sources and claim methodology

Upstream source description

libexpat 2.7.2 through 2.9.0 contains a denial of service vulnerability because XML_ParserReset zeroes the direct byte count but never offsets tracked heap allocations. Attackers can submit a large XML document so later documents on the same reset parser fail with XML_ERROR_NO_MEMORY until it is recreated.

Quoted source text, attributed separately from HOL analysis.