dbcve.org
Hardened ImagesApplication · Redhat

CVE-2026-6732

HIGH · 7.5 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2.15.3 / 4.1.1.30 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in libxml2. This vulnerability occurs when the library processes a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker could exploit this by providing a malicious document, leading to a type confusion error that causes the application to crash. This results in a denial of service (DoS), making the affected system or application unavailable.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-843

A resource is accessed as one type when it was actually allocated as another, so the code misreads memory layout — in interpreters and language runtimes this is frequently a direct path to code execution. It often arises from unchecked casts on attacker-influenced objects. The fix is strict type checks before casts and memory-safe access patterns.

General guidance for the type confusion class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hardened ImagesApplication
Affected:all versions
Jboss Core ServicesApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
Libxml2Framework / library
Affected:>= 2.13.0, < 2.15.3
ViosApplication
Affected:>= 4.1.0, < 4.1.1.30= 4.1.2.0
AixOperating system
Affected:>= 7.2.5, < 7.2.5.12>= 7.3.2, < 7.3.3.3= 7.3.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.15.3 / 4.1.1.30 / 7.2.5.12 or later
Fixed in 2.15.34.1.1.307.2.5.12
Recommended fix High confidence

libxml2 >= 2.15.3

  1. 1. Identify the libxml2 version in use by running: rpm -qa | grep libxml2 (RHEL) or dpkg -l | grep libxml2 (Debian)
  2. 2. For systems using libxml2 >= 2.13.0 and < 2.15.3, upgrade to libxml2 version 2.15.3 or later
  3. 3. For Red Hat Enterprise Linux systems, run: sudo yum update libxml2 or sudo dnf update libxml2
  4. 4. For Debian/Ubuntu systems, run: sudo apt-get update && sudo apt-get install libxml2
  5. 5. For AIX systems, use the AIX security patch bundle corresponding to the fixed versions (7.2.5.12+, 7.3.3.3+)
  6. 6. Restart any services that depend on libxml2 after the update
  7. 7. Verify the updated version matches or exceeds 2.15.3 using: xml2-config --version
Caveat Upgrading libxml2 is generally safe; however, verify application compatibility with the newer libxml2 version as some parsing behaviors may have changed

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6732 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data