dbcve.org
Home Assistant Mcp ServerApplication · Homeassistant Ai

CVE-2026-32111

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 7.0.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-Side Request Forgery (SSRF) in ha-mcp OAuth consent form allows unauthenticated attackers to supply arbitrary URLs that the server will request, enabling internal network reconnaissance. The vulnerability affects three code paths: the OAuth form, REST OAuth tool calls, and WebSocket OAuth tool calls - all lack URL validation before making requests to {ha_url}/api/config.

MitigationUpgrade to ha-mcp version 7.0.0 or later which implements proper URL validation. If upgrade is not immediately possible, disable the OAuth beta feature and use the primary deployment method with pre-configured HOMEASSISTANT_TOKEN.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Home Assistant Mcp ServerApplication
Affected:< 7.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ha-mcp version
    Run 'npm list @homeassistant-alpha/mcp-server' or check your package.json for the @homeassistant-alpha/mcp-server version entry
    Affected if The version is lower than 7.0.0 (e.g., 6.x.x, 5.x.x, etc.)
  2. Determine if OAuth beta feature is active
    Review your ha-mcp configuration file for any OAuth-related settings such as 'oauth', 'oauth2', or 'authorize' endpoints, or check environment variables for OAuth configuration
    Affected if OAuth or OAuth2 settings are present and enabled in the configuration
  3. Check deployment method for token configuration
    Inspect your startup configuration or environment for HOMEASSISTANT_TOKEN variable versus OAuth flow configuration
    Affected if OAuth flow is configured rather than using a pre-configured HOMEASSISTANT_TOKEN for authentication
  4. Verify URL validation is absent
    If you have access to the server logs or can test, observe whether arbitrary URLs supplied to OAuth consent endpoints trigger requests without validation
    Affected if The server accepts and processes URLs without validating they point to the expected Home Assistant instance

You are affected if running ha-mcp version below 7.0.0 with OAuth beta feature enabled, as all three OAuth code paths lack URL validation before requesting the /api/config endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.0 or later
Fixed in 7.0.0
Interim mitigation

Upgrade to ha-mcp version 7.0.0 or later which implements proper URL validation. If upgrade is not immediately possible, disable the OAuth beta feature and use the primary deployment method with pre-configured HOMEASSISTANT_TOKEN.

Recommended fix High confidence

7.0.0

  1. 1. Check current installed version of ha-mcp (Home Assistant MCP Server)
  2. 2. Upgrade to version 7.0.0 or later to obtain the fixed release with URL validation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Home Assistant Mcp Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32111 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data