Skip to content
Web

CVE-2026-3418

9.1
Critical
EPSS 0.57%Aug 7, 2026

Authenticated publisher can upload files to arbitrary server paths, enabling potential RCE.

common questions

Is CVE-2026-3418 being exploited?

Not confirmed. CVE-2026-3418 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.57% probability of exploitation in the next 30 days.

How severe is CVE-2026-3418?

CVE-2026-3418 is rated Critical with a CVSS score of 9.1. 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-3418?

Not known from our data. No patch reference has been recorded for CVE-2026-3418, 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-3418 affect?

CVE-2026-3418 affects System REST API file-upload endpoints, Web application servers handling uploads, Servers with publisher/admin roles enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-3418?

Disable/restrict uploads, revoke publisher rights, and apply vendor patch ASAP.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
System REST API file-upload endpointsWeb application servers handling uploadsServers with publisher/admin roles enabled
impact

Authenticated publisher can write files to server-accessible locations, potentially leading to remote code execution and full system compromise.

action required

Immediate action required

affected versions
WSO2 WSO2 API Control Plane
  • affected>= 4.5.0 and < 4.5.0.53
  • affected>= 4.6.0 and < 4.6.0.17
WSO2 WSO2 API Manager
  • affected>= 4.4.0 and < 4.4.0.67
  • affected>= 4.5.0 and < 4.5.0.52
  • affected>= 4.6.0 and < 4.6.0.16
WSO2 WSO2 API Manager Publisher REST API V4
  • affected>= 9.30.67 and < 9.30.67.156
  • affected>= 9.31.86 and < 9.31.86.141
  • affected>= 9.32.147 and < 9.32.147.44
vendor says fixed in>= 9.33.104 and <= *
WSO2 WSO2 Carbon API Management API
  • affected>= 9.30.67 and < 9.30.67.156
vendor says fixed in>= 9.33.104 and <= *
WSO2 WSO2 Carbon API Management Implementation
  • affected>= 9.30.67 and < 9.30.67.156
  • affected>= 9.31.86 and < 9.31.86.141
  • affected>= 9.32.147 and < 9.32.147.44
vendor says fixed in>= 9.33.104 and <= *
WSO2 WSO2 Traffic Manager
  • affected>= 4.5.0 and < 4.5.0.51
  • affected>= 4.6.0 and < 4.6.0.16
WSO2 WSO2 Universal Gateway
  • affected>= 4.5.0 and < 4.5.0.52
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free