# CVE-2026-19046: NocteDefensor LudusMCP ludus_environment_guides_search ludusEnvironmentGuidesSearch.ts path traversal

> A path traversal vulnerability in LudusMCP allows local attackers to read arbitrary files via the guide_name argument.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **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:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-6j8j-xrrf-px36

## What is CVE-2026-19046?

CVE-2026-19046 is a medium-severity path traversal vulnerability in NocteDefensor LudusMCP, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been detected in NocteDefensor LudusMCP up to 1.0.24. The impacted element is an unknown function of the file src/tools/ludusEnvironmentGuidesSearch.ts of the component ludus_environment_guides_search. Such manipulation of the argument guide_name leads to path traversal. Local access is required to approach this attack. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-19046 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19046 is a medium-severity path traversal vulnerability in NocteDefensor LudusMCP, published on 6 Aug 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-19046 exists.

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

## Sources

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

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