# CVE-2026-32112: ha-mcp has XSS via Unescaped HTML in OAuth Consent Form

> An attacker can execute JavaScript in the operator's browser via XSS in the OAuth consent form if beta OAuth mode is enabled.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-pf93-j98v-25pv, PYSEC-2026-2508

## What is CVE-2026-32112?

CVE-2026-32112 is a medium-severity cross-site scripting vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ha-mcp is a Home Assistant MCP Server. Prior to 7.0.0, the ha-mcp OAuth consent form renders user-controlled parameters via Python f-strings with no HTML escaping. An attacker who can reach the OAuth endpoint and convince the server operator to follow a crafted authorization URL could execute JavaScript in the operator's browser. This affects only users running the beta OAuth mode (ha-mcp-oauth), which is not part of the standard setup and requires explicit configuration. This vulnerability is fixed in 7.0.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

3 open source packages ship an affected version, including ha-mcp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ha-mcp` | PyPI | All versions | 7.0.0 |
| `ha-mcp` | PyPI | All versions | 7.0.0 |
| `ha-mcp` | PyPI | All versions | 7.0.0 |

Products: Homeassistant-Ai Home Assistant Mcp Server.

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

Upgrade ha-mcp to 7.0.0 or later.

## Is CVE-2026-32112 being exploited?

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

## Other vulnerabilities in homeassistant-ai ha-mcp

- [CVE-2026-32111](https://insights.sbomify.com/CVE-2026-32111/): ha-mcp OAuth 2.1 DCR mode enables network reconnaissance via an error oracle (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32112 is a medium-severity cross-site scripting vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32112 in the wild and no public exploit code.

Affected packages and fixed versions:
- ha-mcp (PyPI): affected all versions; fixed in 7.0.0
- ha-mcp (PyPI): affected all versions; fixed in 7.0.0
- ha-mcp (PyPI): affected all versions; fixed in 7.0.0

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-32112/ (Markdown: https://insights.sbomify.com/CVE-2026-32112/index.md)
```

## Sources

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

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