CVE-2026-6732Public exploit

Application crash via mismatched SAX callback context

Published Apr 23, 2026 · Updated Apr 23, 2026

Type confusion in libxml2 2.13.0 through 2.15.2 allows attackers to crash XSD-validating applications via crafted XML documents. xmlParseReference passes xmlParserCtxt instead of ctxt->userData to SAX text callbacks, causing an active xmlSchemaSAXPlug handler to interpret the parser context as its own callback state. The path requires an internal entity reference in an XSD-validated document and produces a reliable application SIGSEGV without reported data disclosure or modification.

CVSS severity6.5
Medium
EPSS probability0.63%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Type confusion in libxml2 2.13.0 through 2.15.2 allows attackers to crash XSD-validating applications via crafted XML documents. xmlParseReference passes xmlParserCtxt instead of ctxt->userData to SAX text callbacks, causing an active xmlSchemaSAXPlug handler to interpret the parser context as its own callback state. The path requires an internal entity reference in an XSD-validated document and produces a reliable application SIGSEGV without reported data disclosure or modification.

The record

CVE
CVE-2026-6732
Published
Apr 23, 2026
Updated
Apr 23, 2026
Vendor
389 Directory Server
Product
Red Hat JBoss Core Services
Classifications
CWE-843, T1499
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 23, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

389 Directory Server · Red Hat JBoss Core ServicesAffected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 6Affected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 10Affected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 7Affected versions are unavailable in this record.
389 Directory Server · Red Hat OpenShift Container PlatformAffected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 9Affected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 8Affected versions are unavailable in this record.

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
6.5Red Hat, Inc.CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-843Access of Resource Using Incompatible Type ('Type Confusion')
T1499Endpoint Denial of Service

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo