CVE-2026-32112ha-mcp has XSS via Unescaped HTML in OAuth Consent Form
Updated under an hour ago ()
Does this affect you?
It affects homeassistant-ai ha-mcp and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 6.8 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-79
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Analyzed
- Record last updated
- Mar 12, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
homeassistant-ai ha-mcp homeassistant_ai:ha_mcp (from the name) | before 7.0.0 | CNA record |
homeassistant-ai home_assistant_mcp_server homeassistant-ai:home_assistant_mcp_server | before 7.0.0 | NVD |
References
- https://github.com/homeassistant-ai/ha-mcp/security/advisories/GHSA-pf93-j98v-25pvx-refsource-confirm, vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.