CVE-2026-3415

XML External Entity (XXE) Injection via Schema Validation in Multiple WSO2 Products Allows File Reading and Denial of Service

HIGH
8.7
CVSS Score
Published: August 6, 2026 at 05:32 PM UTC
Updated: October 28, 2026 at 08:08 AM UTC
6 products affected across 1 vendorAPI ManagerAPI Control PlaneTraffic Manager

Using WSO2 API Manager by WSO2?

Get instant alerts when new vulnerabilities affect WSO2 API Manager - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.7
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 4.5.0.54, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.0.472, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.1.91, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.0.254, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.0.194, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.0.105, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.4.0.68, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.0.53, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.2.0 (unknown)
Affected range stops below 6.7.206.594, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7.210.95, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.20.74.398, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.28.116.412, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.29.120.228, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.30.67.158, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.31.86.147, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.32.147.38, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 9.33.61 (unaffected)
Affected range stops below 6.7.206.594, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7.210.95, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.20.74.398, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.28.116.412, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.29.120.228, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.30.67.158, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.31.86.147, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.32.147.38, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 9.33.61 (unaffected)
Affected range stops below 4.5.0.52, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.0.53, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.16, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHed10eef1-636d-4fbe-9993-6890dfa878f8
Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-776

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card