# CVE-2026-81847: MAA-AI MaaMCP pipeline_tools.py load_pipeline path traversal

> Remote attackers can exploit a path traversal vulnerability in MaaMCP's pipeline tools to read or modify arbitrary files.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-gq99-8fvp-vvg9

## What is CVE-2026-81847?

CVE-2026-81847 is a medium-severity path traversal vulnerability in MAA-AI MaaMCP, published on 27 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in MAA-AI MaaMCP up to 1.1.1.dev6+g2e4a41287. The affected element is the function save_pipeline/load_pipeline of the file pipeline_tools.py. Performing a manipulation results in path traversal. The attack can be initiated remotely. The exploit has been made public and could be used. The patch is named c93ef45cba75295eba26d9ff1ffb9202a91c6150. To fix this issue, it is recommended to deploy a patch.

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

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


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

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

## Is CVE-2026-81847 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81847 is a medium-severity path traversal vulnerability in MAA-AI MaaMCP, published on 27 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81847 exists.

Affected product: MAA-AI MaaMCP. 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-81847/ (Markdown: https://insights.sbomify.com/CVE-2026-81847/index.md)
```

## Sources

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

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