# CVE-2026-117560: ATXP Gemini CLI Extension through 1.0.0 OS Command Injection via MCP Tools


- **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:** 28 Oct 2026
- **Also known as:** GHSA-w542-83fj-2ghf

## What is CVE-2026-117560?

CVE-2026-117560 is a high-severity vulnerability in atxp gemini-cli-extension, published on 27 Oct 2026. 

### Official description

ATXP Gemini CLI extension through 1.0.0 contains an OS command injection vulnerability in runAtxp() that allows attackers to execute shell commands through unsanitized MCP tool parameters. Attackers can plant instructions in email or SMS content to inject $() or backtick substitutions into parameters like message_id, subject, or query, running commands as the user.

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

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


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

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

## Is CVE-2026-117560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117560 is a high-severity vulnerability in atxp gemini-cli-extension, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117560 in the wild and no public exploit code.

Affected product: atxp gemini-cli-extension. 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-117560/ (Markdown: https://insights.sbomify.com/CVE-2026-117560/index.md)
```

## Sources

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

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