XXE Protection Bypass in Apache CXF WSDL Imports

Apache CXF reads a top-level WSDL through its hardened StaxUtils path, which disables XML DTDs and external entities. However, any <wsdl:import> or <xsd:import> referenced from that top-level WSDL is handed off to WSDL4J, which does not disable DOCTYPE declarations or external entities. As a result, the protections applied to the top-level document do not extend to imported documents, leaving imported WSDL/XSD content vulnerable to XML External Entity (XXE) attacks. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Apache CXF implements XML External Entity (XXE) protection by disabling DTDs and external entities when parsing top-level WSDL documents through its hardened StaxUtils path. However, this protection has a critical gap: when the top-level WSDL contains <wsdl:import> or <xsd:import> statements, CXF delegates parsing of those referenced documents to WSDL4J, which lacks XXE protections. This creates a privilege escalation scenario where attackers bypass the hardened parser by embedding malicious external entity definitions in imported WSDL or XSD files. Organizations using Apache CXF for web service integration are affected, particularly those processing WSDL from untrusted sources or accepting dynamic WSDL references. The vulnerability is particularly dangerous in microservices architectures where WSDL imports chain across multiple service definitions.

Casky's 322 matching skills, powered by Claude's extended reasoning capabilities, detect this vulnerability through analysis of MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would observe detection patterns centered on XML parsing anomalies: the platform identifies discrepancies between parent document validation and child document handling, flags XXE-style entity expansion attempts in import chains, and detects attempts to exfiltrate data via out-of-band XXE channels. The skills specifically correlate CXF's StaxUtils calls with subsequent WSDL4J invocations, surfacing the trust boundary violation. Security teams would see findings highlighting imported schema references lacking entity validation, suspicious DOCTYPE declarations in imported files, and parameter entity definitions attempting to read local system files—patterns characteristic of CVE-2026-65432 exploitation.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-65432.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-65432

Casky has 322 skills that investigate the attack patterns behind CVE-2026-65432. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn