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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
Which versions are affected by CVE-2026-32111?
3 open source packages ship an affected version, including ha-mcp. It affects 1 product.
| Package | 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 include Homeassistant-Ai Home Assistant Mcp Server.
How do I fix CVE-2026-32111?
Upgrade ha-mcp to 7.0.0 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
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
Sources
Also known as GHSA-fmfg-9g7c-3vq7, PYSEC-2026-2507.