# CVE-2026-9467: debugmcp mcp-debugger server.ts handleGetSourceContext path traversal

> Remote attackers can exploit a path traversal flaw in the debugmcp mcp-debugger to read arbitrary files from the server.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-8744-whr8-7m8p

## What is CVE-2026-9467?

CVE-2026-9467 is a medium-severity path traversal vulnerability in debugmcp mcp-debugger, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in debugmcp mcp-debugger up to 0.20.0. Impacted is the function handleGetSourceContext of the file src/server.ts. The manipulation leads to path traversal. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-9467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9467 is a medium-severity path traversal vulnerability in debugmcp mcp-debugger, published on 25 May 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-9467 exists.

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

## Sources

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

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