# CVE-2026-3418: Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution

> Authenticated publishers can upload arbitrary files via the System REST API, potentially leading to remote code execution on WSO2 API Management products.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-xx79-g5wr-vq89

## What is CVE-2026-3418?

CVE-2026-3418 is a critical vulnerability in WSO2 API Control Plane, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The System REST API accepts user-supplied file uploads without enforcing sufficient validation on the file type or destination, allowing files to be written to arbitrary server-accessible locations. Exploitation requires authenticated administrative access with publisher privileges.

Successful exploitation permits an authenticated publisher to upload files to server-accessible locations. Depending on the deployment environment and how uploaded files are handled, this could lead to the execution of uploaded content, potentially resulting in remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-3418?


## How do I fix CVE-2026-3418?

No fix has been published for CVE-2026-3418 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3418 being exploited?

There is no known exploitation of CVE-2026-3418 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3418 and fix it if it is affected.

What it is: CVE-2026-3418 is a critical vulnerability in WSO2 API Control Plane, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3418 in the wild and no public exploit code.

Affected product: WSO2 API Control Plane. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3418/ (Markdown: https://insights.sbomify.com/CVE-2026-3418/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3418
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3418
- OSV: https://osv.dev/vulnerability/CVE-2026-3418

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3418/
Summaries are generated and may contain mistakes; the official description above is the record.