# CVE-2026-10264: lharries whatsapp-mcp Send API Endpoint main.go SendMessageRequest path traversal

> An attacker can exploit path traversal in the Send API endpoint to read or modify arbitrary files on the server.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-frgv-ppw5-432r

## What is CVE-2026-10264?

CVE-2026-10264 is a medium-severity path traversal vulnerability in lharries whatsapp-mcp, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in lharries whatsapp-mcp 0.0.1. Affected by this vulnerability is the function SendMessageRequest of the file whatsapp-bridge/main.go of the component Send API Endpoint. This manipulation of the argument mediaPath causes path traversal. The exploit has been publicly disclosed and may be utilized. Patch name: 6657cdceadd361e8fbe824afe9d00b4504009a5d. It is recommended to apply a patch to fix this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-10264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10264 is a medium-severity path traversal vulnerability in lharries whatsapp-mcp, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10264 exists.

Affected product: lharries whatsapp-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-10264/ (Markdown: https://insights.sbomify.com/CVE-2026-10264/index.md)
```

## Sources

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

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