# CVE-2026-115727: AgenticSeek before commit 409840c RCE via Exposed Werkzeug Debugger in llm_server


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-r5cp-9ffr-m5mf

## What is CVE-2026-115727?

CVE-2026-115727 is a critical vulnerability in Fosowl AgenticSeek, published on 23 Oct 2026. 

### Official description

AgenticSeek before commit 409840c contains a remote code execution vulnerability because llm_server/app.py hardcodes Flask debug mode while binding to all interfaces. Attackers who reach the server port and obtain the derivable Werkzeug debugger PIN can execute Python code and operating system commands with llm_server privileges.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2026-115727 being exploited?

There is no known exploitation of CVE-2026-115727 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115727 is a critical vulnerability in Fosowl AgenticSeek, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115727 in the wild and no public exploit code.

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

## Sources

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

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