BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-65432High confidence

Apache CXF: XXE via WSDL/XSD import parsing

Apache Software Foundation · Apache CXF

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 631 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.65% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache CXF and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 631 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-65432 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityApache CXF: Apache CXF: XML External Entity (XXE) vulnerability via WSDL/XSD import parsing
631 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3
Summary
A flaw was found in Apache CXF. The framework's initial processing of a Web Services Description Language (WSDL) document disables XML DTDs (Document Type Definitions) and external entities. However, any WSDL or XML Schema Definition (XSD) documents imported by the top-level WSDL are processed by a different component, WSDL4J, which does not apply these same security protections. This oversight allows an attacker to exploit XML External Entity (XXE) vulnerabilities through imported WSDL/XSD content, potentially leading to information disclosure or denial of service.
Remediation
Update Apache CXF to a version that includes the fix. Disable DTD processing and external entity resolution in XML parsers. Avoid processing untrusted WSDL/XSD imports.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-53856

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 631 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Restriction of XML External Entity Reference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-611 ↗

CWE-611: Improper Restriction of XML External Entity Reference. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-611
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2867RealObjects PDFreactor: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in RealObjects PDFreactor ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2682Apache CXF: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache CXF ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Aug 2026, published on 12 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-57819 Référence CVE CVE-2026-59083 https://www.cve.org/CVERecord?id=CVE-2026-59083 Référence CVE CVE-2026-59084 https://www.cve.org/CVERecord?id=CVE-2026-59084 Référence CVE CVE-2026-59935 https://www.cve.org/CVERecord?id=CVE-2026-59935 Référence CVE CVE-2026-59936 https://www.cve.org/CVERecord?id=CVE-2026-59936 Référence CVE CVE-2026-59937 https://www.cve.org/CVERecord?id=CVE-2026-59937 Référence CVE CVE-2026-59938 https://www.cve.org/CVERecord?id=CVE-2026-59938 Référence CVE CVE-2026-60147 https://www.cve.org/CVERecord?id=CVE-2026-60147 Référence CVE CVE-2026-64958 https://www.cve.org/CVERecord?id=CVE-2026-64958 Référence CVE CVE-2026-65432 https://www.cve.org/CVERecord?id=CVE-2026-65432 Référence CVE CVE-2026-66053 https://www.cve.org/CVERecord?id=CVE-2026-66053 Référence CVE CVE-2026-66142 https://www.cve.org/CVERecord?id=CVE-2026-66142 Référence CVE CVE-2026-66143 https://www.cve.org/CVERecord?id=CVE-2026-66143 Référence CVE CVE-2026-66144 https://www.cve.org/CVERecord?id=CVE-2026-66144 Référence CVE CVE-2026-66713 https://www.cve.org/CVERecord?id=CVE-2026-66713 Référence CVE CVE-2026-6790 https://www.cve.org/CVERecord?id=CVE-2026-6790 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-60589 Référence CVE CVE-2026-61308 https://www.cve.org/CVERecord?id=CVE-2026-61308 Référence CVE CVE-2026-62243 https://www.cve.org/CVERecord?id=CVE-2026-62243 Référence CVE CVE-2026-6321 https://www.cve.org/CVERecord?id=CVE-2026-6321 Référence CVE CVE-2026-6322 https://www.cve.org/CVERecord?id=CVE-2026-6322 Référence CVE CVE-2026-64607 https://www.cve.org/CVERecord?id=CVE-2026-64607 Référence CVE CVE-2026-64958 https://www.cve.org/CVERecord?id=CVE-2026-64958 Référence CVE CVE-2026-65182 https://www.cve.org/CVERecord?id=CVE-2026-65182 Référence CVE CVE-2026-65183 https://www.cve.org/CVERecord?id=CVE-2026-65183 Référence CVE CVE-2026-65432 https://www.cve.org/CVERecord?id=CVE-2026-65432 Référence CVE CVE-2026-65637 https://www.cve.org/CVERecord?id=CVE-2026-65637 Référence CVE CVE-2026-65898 https://www.cve.org/CVERecord?id=CVE-2026-65898 Référence CVE CVE-2026-65899 https://www.cve.org/CVERecord?id=CVE-2026-65899 Référence CVE CVE-2026-65900 https://www.cve.org/CVERecord?id=CVE-2026-65900 Référence CVE CVE-2026-65901 https://www.cve.org/CVERecord?id=CVE-2026-65901 Référence CVE CVE-2026-65902 https://www.cve.org/CVERecord?id=CVE-2026-65902 Référence CVE CVE-2026-65903 https://www.cve.org/CVERecord?id=CVE-2026-65903 Référence CVE CVE-2026-65904 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027268Apache Software FoundationのApache CXFにおけるXML 外部エンティティの脆弱性

Apache CXFは、強化されたStaxUtils経路を通じてトップレベルのWSDLを読み込みます。この経路ではXMLのDTDおよび外部エンティティが無効化されています。しかし、そのトップレベルのWSDLから参照される任意の<wsdl:import>や<xsd:import>はWSDL4Jに渡されますが、WSDL4JではDOCTYPE宣言や外部エンティティが無効化されていません。その結果、トップレベル文書に適用された保護はインポートされた文書には及ばず、インポートされたWSDL/XSDの内容はXML外部エンティティ(XXE)攻撃に対して脆弱な状態になっています。ユーザーには、本問題を修正したバージョン4.2.3、4.1.8、または3.6.12へのアップグレードを推奨します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Update Apache CXF to a version that includes the fix. Disable DTD processing and external entity resolution in XML parsers. Avoid processing untrusted WSDL/XSD imports.
04

Evidence and provenance

Published 6 Aug 2026 · Last source change 7 Aug 2026, 00:01 UTC · CWE-611 · Improper Restriction of XML External Entity Reference

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-53856
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-jaxws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-simple as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-management as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-json-basic as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-security-jose as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security-saml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-transports-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-addr as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-mex as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-policy as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-rm as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-wsdl as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-services-sts-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-java2ws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-validator as a component of Red Hat build of Apache Camel 4 for Quarkus 3; and 682 more
    After
    camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-jaxws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-simple as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-management as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-json-basic as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-security-jose as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security-saml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-transports-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-addr as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-mex as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-policy as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-rm as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-wsdl as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-services-sts-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-java2ws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-validator as a component of Red Hat build of Apache Camel 4 for Quarkus 3; and 601 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-65432 · cve.blacktree.nl