# CVE-2026-10044: ai-goofish-monitor Unauthenticated Arbitrary File Read via GET /api/prompts/

> Unauthenticated attackers can read arbitrary files on Windows deployments by bypassing path traversal guards in the prompts API endpoint.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-93rg-qjp9-mg35

## What is CVE-2026-10044?

CVE-2026-10044 is a high-severity path traversal vulnerability in Usagi-org ai-goofish-monitor, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Usagi-org ai-goofish-monitor contains an unauthenticated arbitrary file read vulnerability in the GET /api/prompts/{filename} endpoint on Windows deployments that allows unauthenticated remote attackers to read arbitrary files by supplying absolute Windows paths or backslash-based traversal sequences. Attackers can bypass the incomplete path traversal guard, which only blocks forward slashes and '..', by providing absolute paths such as Windows system file locations, causing os.path.join to discard the intended prompts directory prefix and expose files accessible to the application process.

Weakness: CWE-36 (Absolute Path Traversal)

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


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

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

## Is CVE-2026-10044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10044 is a high-severity path traversal vulnerability in Usagi-org ai-goofish-monitor, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10044 exists.

Affected product: Usagi-org ai-goofish-monitor. 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-10044/ (Markdown: https://insights.sbomify.com/CVE-2026-10044/index.md)
```

## Sources

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

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