NVD / CVE Program· CNA WSO2

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

Noroxi assessment

Priority: Monitor (action score 34/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.7 · v3.1—No exploit No fix recorded

EUVD-2026-54208

Published: Aug 6, 2026
Updated: Oct 28, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-776

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 34 / 40 · 8.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · WSO2: 8.7; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.54affected
- 4.6.0 and later · before 4.6.0.17affected
WSO2 WSO2 API Manager
- before 3.2.0unknown
- 3.2.0 and later · before 3.2.0.472affected
- 3.2.1 and later · before 3.2.1.91affected
- 4.1.0 and later · before 4.1.0.254affected
- 4.2.0 and later · before 4.2.0.194affected
- 4.3.0 and later · before 4.3.0.105affected
- 4.4.0 and later · before 4.4.0.68affected
- 4.5.0 and later · before 4.5.0.53affected
- 4.6.0 and later · before 4.6.0.16affected
WSO2 WSO2 Carbon API Gateway
- 6.7.206 and later · before 6.7.206.594affected
- 6.7.210 and later · before 6.7.210.95affected
- 9.20.74 and later · before 9.20.74.398affected
- 9.28.116 and later · before 9.28.116.412affected
- 9.29.120 and later · before 9.29.120.228affected
- 9.30.67 and later · before 9.30.67.158affected
- 9.31.86 and later · before 9.31.86.147affected
- 9.32.147 and later · before 9.32.147.38affected
- 9.33.61 and laternot affected
WSO2 WSO2 Carbon API Management Implementation
- 6.7.206 and later · before 6.7.206.594affected
- 6.7.210 and later · before 6.7.210.95affected
- 9.20.74 and later · before 9.20.74.398affected
- 9.28.116 and later · before 9.28.116.412affected
- 9.29.120 and later · before 9.29.120.228affected
- 9.30.67 and later · before 9.30.67.158affected
- 9.31.86 and later · before 9.31.86.147affected
- 9.32.147 and later · before 9.32.147.38affected
- 9.33.61 and laternot affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.52affected
- 4.6.0 and later · before 4.6.0.16affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.53affected
- 4.6.0 and later · before 4.6.0.16affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

CVE-2026-4052Privilege Escalation via Token Endpoint in WSO2 API Manager (APIM 4.x/IS as Resident Key Manager)
39Monitor
CVE-2025-11969Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized Administrative Actions
37Monitor
CVE-2025-14561Access Control Bypass via Publisher REST APIs in Multiple WSO2 Products Allows Cross-Tenant Operations
36Monitor

Published before and after this one in the same product

Later →CVE-2026-3418Aug 6, 2026 · Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution
36Monitor
Later →CVE-2025-6508Aug 6, 2026 · User Interface Misrepresentation via Swagger UI Try-out Console in WSO2 API Manager Allows Sensitive Information Exposure or Unintended Requests
17Monitor
Later →CVE-2025-5802Sep 15, 2026 · Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).