# CVE-2026-32111: ha-mcp OAuth 2.1 DCR mode enables network reconnaissance via an error oracle

> An unauthenticated attacker can perform internal network reconnaissance via an error oracle in the beta OAuth consent form of the Home Assistant MCP Server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-fmfg-9g7c-3vq7, PYSEC-2026-2507

## What is CVE-2026-32111?

CVE-2026-32111 is a medium-severity server-side request forgery vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ha-mcp is a Home Assistant MCP Server. Prior to 7.0.0, the ha-mcp OAuth consent form (beta feature) accepts a user-supplied ha_url and makes a server-side HTTP request to {ha_url}/api/config with no URL validation. An unauthenticated attacker can submit arbitrary URLs to perform internal network reconnaissance via an error oracle. Two additional code paths in OAuth tool calls (REST and WebSocket) are affected by the same primitive. The primary deployment method (private URL with pre-configured HOMEASSISTANT_TOKEN) is not affected. This vulnerability is fixed in 7.0.0.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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-32111?

Upgrade ha-mcp to 7.0.0 or later.

## Is CVE-2026-32111 being exploited?

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

## Other vulnerabilities in homeassistant-ai ha-mcp

- [CVE-2026-32112](https://insights.sbomify.com/CVE-2026-32112/): ha-mcp has XSS via Unescaped HTML in OAuth Consent Form (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32111 is a medium-severity server-side request forgery vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32111 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-32111/ (Markdown: https://insights.sbomify.com/CVE-2026-32111/index.md)
```

## Sources

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

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