# CVE-2026-15528: lamaalrajih kicad-mcp path_validator.py protection mechanism

> Local attackers can bypass path validation in kicad-mcp to access or modify arbitrary files via manipulated project or schematic paths.

- **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: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:** 13 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-c7fc-wmwf-cvvh

## What is CVE-2026-15528?

CVE-2026-15528 is a medium-severity path traversal vulnerability in lamaalrajih kicad-mcp, published on 13 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in lamaalrajih kicad-mcp up to 3.3.1. This issue affects some unknown processing of the file kicad_mcp/utils/path_validator.py. Performing a manipulation of the argument project_path/schematic_path results in protection mechanism failure. Attacking locally is a requirement. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

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

## Is CVE-2026-15528 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15528 is a medium-severity path traversal vulnerability in lamaalrajih kicad-mcp, published on 13 Jul 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-15528 exists.

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

## Sources

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

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