# CVE-2026-15189: aerostackdev aerostack-mcp mcp-whatsapp upload_media server-side request forgery

> Remote attackers can exploit the upload_media function to perform server-side request forgery via the media_url argument.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-rx6v-r244-h59w

## What is CVE-2026-15189?

CVE-2026-15189 is a medium-severity server-side request forgery vulnerability in aerostackdev aerostack-mcp, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in aerostackdev aerostack-mcp up to 6315dfde7df0a15aaf743f88d91347115e09ba23. Affected by this issue is the function upload_media of the component mcp-whatsapp. Such manipulation of the argument media_url leads to server-side request forgery. The attack may be launched remotely. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-15189 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15189 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15189 is a medium-severity server-side request forgery vulnerability in aerostackdev aerostack-mcp, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15189 exists.

Affected product: aerostackdev aerostack-mcp. 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-15189/ (Markdown: https://insights.sbomify.com/CVE-2026-15189/index.md)
```

## Sources

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

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