# CVE-2026-117569: Kali-GPT through commit a608c74 OS Command Injection via MCP Scanner Tool Parameters


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-qqg8-6hv5-w2xr

## What is CVE-2026-117569?

CVE-2026-117569 is a high-severity vulnerability in alishahid74 kali-gpt, published on 27 Oct 2026. 

### Official description

Kali-GPT through commit a608c74 contains an OS command injection vulnerability in execute_tool() in kali_gpt/tools/mcp_server.py that allows MCP clients to run commands via unsanitized scanner parameters. Attackers or prompt-injected agents can embed shell metacharacters in parameters like target, ports, domain, wordlist, or url, executed via subprocess.run with shell=True as the MCP server user.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-117569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117569 is a high-severity vulnerability in alishahid74 kali-gpt, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117569 in the wild and no public exploit code.

Affected product: alishahid74 kali-gpt. 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-117569/ (Markdown: https://insights.sbomify.com/CVE-2026-117569/index.md)
```

## Sources

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

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