Skip to main content
VulnerabilityPublished

ha-mcp: Add-on settings and policy routes are reachable without authentication at the bare root path

Affects ha-mcpSource GCVE Database

0

CVSS 6.5 Medium : upgrade to 7.10.0 when convenient.

Data as of 8 Jul 2026, 13:40 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 7.10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

What to do

Upgrade ha-mcp to 7.10.0.

Affected software

ProductAffectedFixed in
PyPIha-mcpAffected
  • <7.10.0
Fixed in
  • 7.10.0

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

AI-suggested

A fix is available and included in ha-mcp add-on version 7.10.0 and later. The fix restricts root path access on port 9583 to Home Assistant ingress only, which originates from the Supervisor IP, returning HTTP 403 to unauthorized callers. Operators should upgrade to version 7.10.0 or later when available. The fix is also available on the development channel (7.6.0.dev393 or later) if immediate mitigation is desired. There is no need to switch channels solely for this fix as the risk surface is low and limited to add-on mode. Until patched, operators should ensure that port 9583 is not exposed without proper network controls or reverse proxy restrictions.

Description

In ha-mcp add-on mode for Home Assistant, certain settings and policy routes are accessible without authentication at the bare root path on port 9583 in versions prior to 7.10.0. This allows any client able to reach this port to read or modify add-on configurations, toggle feature flags, manage backups, restart the add-on, and alter approval policies if enabled, without requiring authentication. The vulnerability does not expose Home Assistant data, credentials, or allow code execution. The issue is fixed by restricting root path access to Home Assistant ingress only, with the fix included in versions 7.10.0 and later.

References

Community reviews

Loading reviews…