Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-3415

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

High8.7EPSS 0.49%
Published
Updated
Reserved
Assigned by
WSO2

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.

Scores

CVSS scores of CVE-2026-3415, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1High8.7CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H
NVDNVD · Deferred3.1High8.7CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.49% · top 58% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.7.

Weakness

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 3.2.0
    • affected 3.2.0 – < 3.2.0.472
    • affected 3.2.1 – < 3.2.1.91
    • affected 4.1.0 – < 4.1.0.254
    • affected 4.2.0 – < 4.2.0.194
    • affected 4.3.0 – < 4.3.0.105
    • affected 4.4.0 – < 4.4.0.68
    • affected 4.5.0 – < 4.5.0.53
    • affected 4.6.0 – < 4.6.0.16

  • WSO2 · WSO2 Universal Gateway

    • affected 4.5.0 – < 4.5.0.53
    • affected 4.6.0 – < 4.6.0.16

  • WSO2 · WSO2 Traffic Manager

    • affected 4.5.0 – < 4.5.0.52
    • affected 4.6.0 – < 4.6.0.16

  • WSO2 · WSO2 API Control Plane

    • affected 4.5.0 – < 4.5.0.54
    • affected 4.6.0 – < 4.6.0.17

  • WSO2 · WSO2 Carbon API Gateway

    • affected 6.7.206 – < 6.7.206.594
    • affected 6.7.210 – < 6.7.210.95
    • affected 9.20.74 – < 9.20.74.398
    • affected 9.28.116 – < 9.28.116.412
    • affected 9.29.120 – < 9.29.120.228
    • affected 9.30.67 – < 9.30.67.158
    • affected 9.31.86 – < 9.31.86.147
    • affected 9.32.147 – < 9.32.147.38
    • unaffected 9.33.61 – ≤ *

  • WSO2 · WSO2 Carbon API Management Implementation

    • affected 6.7.206 – < 6.7.206.594
    • affected 6.7.210 – < 6.7.210.95
    • affected 9.20.74 – < 9.20.74.398
    • affected 9.28.116 – < 9.28.116.412
    • affected 9.29.120 – < 9.29.120.228
    • affected 9.30.67 – < 9.30.67.158
    • affected 9.31.86 – < 9.31.86.147
    • affected 9.32.147 – < 9.32.147.38
    • unaffected 9.33.61 – ≤ *

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5001/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5001/#solution

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-3415 badge
[![CVE-2026-3415](https://trackcve.app/badge/CVE-2026-3415.svg)](https://trackcve.app/cve/CVE-2026-3415)

Record last updated .