CVE-2026-56403

Description

A flaw was found in libexpat. An integer overflow vulnerability exists in the storeAtts function. This flaw could allow an attacker to corrupt memory, leading to a denial of service, information disclosure, or potentially arbitrary code execution, compromising the integrity and confidentiality of data.

Statement

A moderate-severity flaw was found in libexpat, which is provided by Red Hat Enterprise Linux (expat, compat-expat1, and mingw-expat), Red Hat In-Vehicle OS, and Red Hat JBoss Core Services, and is also bundled in container images shipped with products such as Red Hat OpenShift AI, Red Hat Ansible Automation Platform, and other Red Hat services offerings. An integer overflow in the storeAtts function during XML parsing allows a crafted XML document to trigger memory corruption, which can result in a denial of service, information disclosure, or potentially arbitrary code execution. Red Hat rates this flaw as Moderate (CVSS 3.1 score 6.9, AV:L/AC:H/PR:N/UI:N) because exploitation requires high attack complexity and an attacker must be able to supply a crafted XML document to an application that processes it with the affected library on the same system. Fixes for the affected Red Hat products are currently deferred: they will be delivered in a future planned update rather than an immediate security erratum, and the residual risk until then is limited to applications that parse attacker-controlled XML input using a vulnerable libexpat build. For Fedora, remediation is delegated to the Fedora community, which is pursuing a fix. This severity rating is consistent with the upstream assessment.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream project has addressed this issue in libexpat 2.8.2, so updating affected systems to packages built from that version or a later one, once available, resolves the flaw.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.96.96.9
Attack VectorLocalLocalLocal
Attack ComplexityHighHighHigh
Privileges RequiredNoneNoneNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityHighHighHigh
Integrity ImpactHighHighHigh
Availability ImpactLowLowLow

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

NVD: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

cve.org: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability

This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.

Integrity

Technical Impact: Modify Memory

If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.

Confidentiality,Availability,Access Control

Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism

This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.

Availability,Other

Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)

If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.

Access Control

Technical Impact: Bypass Protection Mechanism

If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.

Access Control

Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart

If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].

Frequently Asked Questions

Want to get errata notifications? Sign up here.