# carbon-apimgt does not properly restrict uploaded files

Advisory record · `GHSA-p6jf-79j3-33f3`

- **Identifiers:** `GHSA-p6jf-79j3-33f3` · `CVE-2025-13590`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-434](https://cwe.mitre.org/data/definitions/434.html)
- **Tags:** [Unrestricted file upload](https://agentprime.io/advisories/tag/file-upload.md)
- **Published:** 19 Feb 2026
- **Updated:** 14 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Feb 2026, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1` (Maven): affected `<9.32.167`; fixed in `9.32.167`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 package is affected in versions before 9.32.167. An attacker with administrative privileges can upload an arbitrary file to a user-controlled location in the deployment through a system REST API, and successful uploads may lead to remote code execution. Upgrade to version 9.32.167, which is the listed fix. No workaround is listed.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`, from CNA (WSO2)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0077, the 56th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p6jf-79j3-33f3)

## Sources

- [GitHub Advisory Database: GHSA-p6jf-79j3-33f3](https://github.com/advisories/GHSA-p6jf-79j3-33f3)
- [OSV: GHSA-p6jf-79j3-33f3](https://osv.dev/vulnerability/GHSA-p6jf-79j3-33f3)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-13590>
- <https://github.com/wso2/carbon-apimgt/pull/13560>
- <https://github.com/wso2/carbon-apimgt/commit/49a6427b39a5d9552ce97430858bb4b1912a3044>
- <https://github.com/wso2/carbon-apimgt>
- <https://github.com/wso2/carbon-apimgt/releases/tag/v9.32.167>
- <https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4849>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-p6jf-79j3-33f3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p6jf-79j3-33f3/>. Everything for agents: <https://agentprime.io/llms.txt>.