Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.49% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-3415High confidence
XML External Entity (XXE) Injection via Schema Validation in Multiple WSO2 Products Allows File Reading and Denial of Service
WSO2 · WSO2 API Manager
8.7HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs WSO2 WSO2 API Manager and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
The XML and schema validation functionalities within the SchemaValidator Mediator process XML input as part of validation flows. Under certain conditions, the XML parser allows the resolution of external entities when handling user-supplied XML content during validation operations. This behavior can occur when an attacker supplies crafted XML payloads to the relevant mediator flows with sufficient privileges. Successful exploitation may allow a highly privileged actor to read files accessible within the server hosting the affected product. Additionally, it may be possible to trigger outbound requests to unintended internal or external locations, depending on the server environment and network configuration. Specially crafted XML payloads can also lead to excessive resource consumption during parsing, impacting the availability of the product.
What
The XML and schema validation functionalities within the SchemaValidator Mediator process XML input as part of validation flows. Under certain conditions, the XML parser allows the resolution of external entities when handling user-supplied XML content during validation operations. This behavior can occur when an attacker supplies crafted XML payloads to the relevant mediator flows with sufficient privileges. Successful exploitation may allow a highly privileged actor to read files accessible within the server hosting the affected product. Additionally, it may be possible to trigger outbound requests to unintended internal or external locations, depending on the server environment and network configuration. Specially crafted XML payloads can also lead to excessive resource consumption during parsing, impacting the availability of the product.
Why
The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.
How
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
The XML and schema validation functionalities within the SchemaValidator Mediator process XML input as part of validation flows. Under certain conditions, the XML parser allows the resolution of external entities when handling user-supplied XML content during validation operations. This behavior can occur when an attacker supplies crafted XML payloads to the relevant mediator flows with sufficient privileges. Successful exploitation may allow a highly privileged actor to read files accessible within the server hosting the affected product. Additionally, it may be possible to trigger outbound requests to unintended internal or external locations, depending on the server environment and network configuration. Specially crafted XML payloads can also lead to excessive resource consumption during parsing, impacting the availability of the product.
Why
The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.
How
An attacker operating through a network path may attempt exploitation with elevated privileges. 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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 Recursive Entity References in DTDs ('XML Entity Expansion') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- High: elevated access is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-776 ↗
CWE-776: Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion'). The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.
- 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:H/UI:N/S:C/C:H/I:N/A:HCommon 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.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- 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.
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. - Patch available
- Affected
- WSO2 Carbon API Management Implementation: 9.28.116 < 9.28.116.412, 6.7.210 < 6.7.210.95, 9.32.147 < 9.32.147.38, 6.7.206 < 6.7.206.594, 9.31.86 < 9.31.86.147, 9.30.67 < 9.30.67.158, 9.29.120 < 9.29.120.228, 9.20.74 < 9.20.74.398
- WSO2 API Manager: 4.1.0 < 4.1.0.254, 3.2.1 < 3.2.1.91, 4.4.0 < 4.4.0.68, 4.5.0 < 4.5.0.53, 3.2.0 < 3.2.0.472, 4.6.0 < 4.6.0.16, 4.3.0 < 4.3.0.105, 4.2.0 < 4.2.0.194
- WSO2 Universal Gateway: 4.6.0 < 4.6.0.16, 4.5.0 < 4.5.0.53
- WSO2 Carbon API Gateway: 9.28.116 < 9.28.116.412, 9.30.67 < 9.30.67.158, 6.7.210 < 6.7.210.95, 9.31.86 < 9.31.86.147, 9.32.147 < 9.32.147.38, 9.20.74 < 9.20.74.398, 9.29.120 < 9.29.120.228, 6.7.206 < 6.7.206.594
- WSO2 API Control Plane: 4.5.0 < 4.5.0.54, 4.6.0 < 4.6.0.17
- WSO2 Traffic Manager: 4.6.0 < 4.6.0.16, 4.5.0 < 4.5.0.52
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 6 Aug 2026 · Last source change 23 Sept 2026, 16:04 UTC · CWE-776 · Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-54208
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- < 3.2.0; 3.2.0 < 3.2.0.472; 3.2.1 < 3.2.1.91; 4.1.0 < 4.1.0.254; 4.2.0 < 4.2.0.194; 4.3.0 < 4.3.0.105; 4.4.0 < 4.4.0.68; 4.5.0 < 4.5.0.53 · Fixed: 9.33.61 ≤ *
- After
- WSO2 API Manager: < 3.2.0, 3.2.0 < 3.2.0.472, 3.2.1 < 3.2.1.91, 4.1.0 < 4.1.0.254, 4.2.0 < 4.2.0.194, 4.3.0 < 4.3.0.105, 4.4.0 < 4.4.0.68, 4.5.0 < 4.5.0.53, 4.6.0 < 4.6.0.16; WSO2 Universal Gateway: 4.5.0 < 4.5.0.53, 4.6.0 < 4.6.0.16; WSO2 Traffic Manager: 4.5.0 < 4.5.0.52, 4.6.0 < 4.6.0.16; WSO2 API Control Plane: 4.5.0 < 4.5.0.54, 4.6.0 < 4.6.0.17; WSO2 Carbon API Gateway: 6.7.206 < 6.7.206.594, 6.7.210 < 6.7.210.95, 9.20.74 < 9.20.74.398, 9.28.116 < 9.28.116.412, 9.29.120 < 9.29.120.228, 9.30.67 < 9.30.67.158, 9.31.86 < 9.31.86.147, 9.32.147 < 9.32.147.38; WSO2 Carbon API Management Implementation: 6.7.206 < 6.7.206.594, 6.7.210 < 6.7.210.95, 9.20.74 < 9.20.74.398, 9.28.116 < 9.28.116.412, 9.29.120 < 9.29.120.228, 9.30.67 < 9.30.67.158, 9.31.86 < 9.31.86.147, 9.32.147 < 9.32.147.38 · Fixed: WSO2 Carbon API Gateway: 9.33.61 ≤ *; WSO2 Carbon API Management Implementation: 9.33.61 ≤ *
CVE published
Fixed release or patch reference recorded
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.