# CVE-2026-117573: hagent through commit 761eec6 OS Command Injection via Arduino and ESP32 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:** 27 Oct 2026
- **Also known as:** GHSA-j5hx-w574-wh9m

## What is CVE-2026-117573?

CVE-2026-117573 is a high-severity vulnerability in masc-ucsc hagent, published on 27 Oct 2026. 

### Official description

hagent through commit 761eec6 contains an OS command injection vulnerability that allows MCP clients to execute shell commands by injecting metacharacters into the args parameter of the hagent_arduino and hagent_esp32 tools. Attackers or prompt-injected agents can supply crafted args interpolated into arduino-cli and idf.py commands run with subprocess.run(shell=True) to execute commands 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-117573?


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

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

## Is CVE-2026-117573 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117573 is a high-severity vulnerability in masc-ucsc hagent, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117573 in the wild and no public exploit code.

Affected product: masc-ucsc hagent. 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-117573/ (Markdown: https://insights.sbomify.com/CVE-2026-117573/index.md)
```

## Sources

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

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