# CVE-2026-116045: 1999AZZAR designer-mcp MCP motion-dev-guidelines.md get_reference path traversal


- **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
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-p45h-7j97-qg29

## What is CVE-2026-116045?

CVE-2026-116045 is a medium-severity vulnerability in 1999AZZAR designer-mcp, published on 25 Oct 2026. 

### Official description

A vulnerability was detected in 1999AZZAR designer-mcp up to 2.1.0. This affects the function get_reference of the file skills/motion-designer/references/motion-dev-guidelines.md of the component MCP Interface. The manipulation of the argument Name results in path traversal. It is possible to launch the attack remotely. The exploit is now public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The patch is identified as c8c2951dcbed9b1710a745993f028317f10a3f10. Applying a patch is advised to resolve this issue.

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

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


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

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

## Is CVE-2026-116045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116045 is a medium-severity vulnerability in 1999AZZAR designer-mcp, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116045 exists.

Affected product: 1999AZZAR designer-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-116045/ (Markdown: https://insights.sbomify.com/CVE-2026-116045/index.md)
```

## Sources

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

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