VulnerabilityPublished 11 Mar 2026

CVE-2026-32111: homeassistant-ai ha-mcp · Server-Side Request Forgery (SSRF)

Affects homeassistant-ai ha-mcpSource CVE Database V5

Compare

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

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% 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:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

Affected software

Product	Affected	Fixed in
homeassistant-aiha-mcp	Affected <7.0.0	Fixed in 7.0.0
GitHubhomeassistant-ai/ha-mcp`pkg:github/homeassistant-ai/ha-mcp`Other threats	Affected <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

To mitigate CVE-2026-32111, organizations should upgrade ha-mcp to version 7.0.0 or later, where the vulnerability is fixed. If immediate upgrade is not feasible, administrators should disable the OAuth consent form beta feature that accepts user-supplied ha_url parameters to prevent SSRF exploitation. Network-level controls such as firewall rules or web application firewalls (WAF) can be configured to restrict outbound HTTP requests from the ha-mcp server to only trusted internal or external endpoints, thereby limiting SSRF impact. Additionally, monitoring and logging HTTP requests initiated by ha-mcp can help detect suspicious SSRF attempts. Implementing strict input validation and URL whitelisting on any user-supplied URLs within the application is critical to prevent SSRF. Finally, segregating the ha-mcp server in a network segment with limited access to sensitive internal resources reduces the risk of internal network reconnaissance.

Description

CVE-2026-32111 is a Server-Side Request Forgery (SSRF) vulnerability in the ha-mcp component of homeassistant-ai versions prior to 7.0.0. The vulnerability arises because the OAuth consent form accepts a user-supplied ha_url and makes an HTTP request to {ha_url}/api/config without validating the URL. This allows unauthenticated attackers to perform internal network reconnaissance by submitting arbitrary URLs. Two other OAuth-related code paths (REST and WebSocket) are also affected by this SSRF primitive. The primary deployment method using a private URL with a pre-configured HOMEASSISTANT_TOKEN is not vulnerable. The issue has a CVSS score of 5.3 (medium severity) and was fixed in version 7.0.

Impact

The primary impact of CVE-2026-32111 is unauthorized internal network reconnaissance through SSRF, which can reveal sensitive infrastructure details to attackers. Organizations using vulnerable versions of ha-mcp in homeassistant-ai may have their internal network topology exposed, potentially allowing attackers to identify internal services, ports, or misconfigurations that are not otherwise accessible externally. This can facilitate subsequent attacks such as lateral movement, privilege escalation, or exploitation of other internal vulnerabilities. Since the vulnerability is unauthenticated and requires no user interaction, it can be exploited remotely by any attacker with network access to the vulnerable service. Although the vulnerability does not directly compromise confidentiality, integrity, or availability of the ha-mcp server itself, the indirect exposure of internal network information can significantly increase the risk profile of affected organizations. The impact is especially critical in environments where homeassistant-ai is deployed in sensitive or segmented networks, such as smart building management, industrial IoT, or enterprise automation systems. The absence of known exploits in the wild currently limits immediate risk, but the medium CVSS score and ease of exploitation warrant prompt remediation.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/homeassistant-ai/ha-mcp/security/advisories/GHSA-fmfg-9g7c-3vq7 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:30 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats