Skip to main content
VulnerabilityPublished

CVE-2026-32112: homeassistant-ai ha-mcp · Cross-site Scripting

Affects homeassistant-ai ha-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 7.0.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.0.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade ha-mcp and homeassistant-ai/ha-mcp to 7.0.0.

Affected software

ProductAffectedFixed in
homeassistant-aiha-mcpAffected
  • <7.0.0
Fixed in
  • 7.0.0
GitHubhomeassistant-ai/ha-mcppkg:github/homeassistant-ai/ha-mcpOther threatsAffected
  • <7.0.0
Fixed in
  • 7.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade ha-mcp to version 7.0.0 or later immediately to apply the fix that properly escapes user input in the OAuth consent form.
  2. Disable the beta OAuth mode (ha-mcp-oauth) if it is not strictly required, as this feature is not part of the standard setup and increases attack surface.
  3. Educate server operators and administrators to be cautious of unsolicited or suspicious OAuth authorization URLs, especially those received via email or messaging.
  4. Implement network-level protections such as web filtering or URL inspection to block known malicious or suspicious OAuth endpoints.
  5. Monitor logs for unusual OAuth authorization requests or patterns that may indicate attempted exploitation.
  6. Consider deploying Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the OAuth consent page context.
  7. Conduct regular security reviews of custom or beta features before enabling them in production environments.
  8. Use multi-factor authentication and session management best practices to limit the impact of stolen tokens or cookies. These steps go beyond generic advice by focusing on the specific beta feature, operator behavior, and layered defenses.

Description

CVE-2026-32112 is a cross-site scripting (XSS) vulnerability in the ha-mcp OAuth consent form of the Home Assistant MCP Server prior to version 7.0.0. The vulnerability arises because user-controlled parameters are rendered using Python f-strings without proper HTML escaping, allowing injection of malicious JavaScript. Exploitation requires an attacker to reach the OAuth endpoint and trick the server operator into visiting a crafted authorization URL. This issue affects only users who have explicitly enabled the beta OAuth mode (ha-mcp-oauth), which is not part of the default setup. The vulnerability has a CVSS score of 6.8, indicating medium severity, with high impact on confidentiality and integrity but no impact on availability. No known exploits are currently in the wild. The vulnerability is fixed in version 7.

References

Community reviews

Loading reviews…