CVE-2026-3415
XML external-entity handling in SchemaValidator allows file disclosure, SSRF, and DoS
Is CVE-2026-3415 being exploited?
Not confirmed. CVE-2026-3415 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-3415?
CVE-2026-3415 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-3415?
Not known from our data. No patch reference has been recorded for CVE-2026-3415, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-3415 affect?
CVE-2026-3415 affects SchemaValidator Mediator, XML validation flows, Application servers hosting the mediator. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-3415?
Disable external entity resolution, restrict/monitor mediator access, harden XML parsers, apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted XML can cause local file disclosure, SSRF (outbound requests), and parser DoS via external-entity resolution when attacker can access mediator flows.
Patch when possible
- affected>= 4.5.0 and < 4.5.0.54
- affected>= 4.6.0 and < 4.6.0.17
- affected< 3.2.0
- affected>= 3.2.0 and < 3.2.0.472
- affected>= 3.2.1 and < 3.2.1.91
- affected>= 4.1.0 and < 4.1.0.254
- affected>= 4.2.0 and < 4.2.0.194
- affected>= 4.3.0 and < 4.3.0.105
- affected>= 4.4.0 and < 4.4.0.68
- affected>= 4.5.0 and < 4.5.0.53
- affected>= 4.6.0 and < 4.6.0.16
- affected>= 6.7.206 and < 6.7.206.594
- affected>= 6.7.210 and < 6.7.210.95
- affected>= 9.20.74 and < 9.20.74.398
- affected>= 9.28.116 and < 9.28.116.412
- affected>= 9.29.120 and < 9.29.120.228
- affected>= 9.30.67 and < 9.30.67.158
- affected>= 9.31.86 and < 9.31.86.147
- affected>= 9.32.147 and < 9.32.147.38
- affected>= 6.7.206 and < 6.7.206.594
- affected>= 6.7.210 and < 6.7.210.95
- affected>= 9.20.74 and < 9.20.74.398
- affected>= 9.28.116 and < 9.28.116.412
- affected>= 9.29.120 and < 9.29.120.228
- affected>= 9.30.67 and < 9.30.67.158
- affected>= 9.31.86 and < 9.31.86.147
- affected>= 9.32.147 and < 9.32.147.38
- affected>= 4.5.0 and < 4.5.0.52
- affected>= 4.6.0 and < 4.6.0.16
- affected>= 4.5.0 and < 4.5.0.53
- affected>= 4.6.0 and < 4.6.0.16
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.