{"answers":{"affected":"3 open source packages ship an affected version, including ha-mcp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32111 in the wild and no public exploit code.","fix":"Upgrade ha-mcp to 7.0.0 or later.","what":"CVE-2026-32111 is a medium-severity server-side request forgery vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32111 and fix it if it is affected.\n\nWhat it is: CVE-2026-32111 is a medium-severity server-side request forgery vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-32111 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ha-mcp (PyPI): affected all versions; fixed in 7.0.0\n- ha-mcp (PyPI): affected all versions; fixed in 7.0.0\n- ha-mcp (PyPI): affected all versions; fixed in 7.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32111/ (Markdown: https://insights.sbomify.com/CVE-2026-32111/index.md)","id":"CVE-2026-32111","markdown":"https://insights.sbomify.com/CVE-2026-32111/index.md","name":"CVE-2026-32111","record":{"aliases":["GHSA-fmfg-9g7c-3vq7","PYSEC-2026-2507"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Home Assistant MCP Server","requires_auth":"none","summary":"An unauthenticated attacker can perform internal network reconnaissance via an error oracle in the beta OAuth consent form of the Home Assistant MCP Server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"home_assistant_mcp_server","vendor":"homeassistant-ai"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ha-mcp OAuth 2.1 DCR mode enables network reconnaissance via an error oracle","id":"CVE-2026-32111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"ha-mcp has XSS via Unescaped HTML in OAuth Consent Form","id":"CVE-2026-32112"},"packages":[{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"ha-mcp","purl":null,"source":"GHSA-fmfg-9g7c-3vq7"},{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"ha-mcp","purl":"pkg:pypi/ha-mcp","source":"GHSA-fmfg-9g7c-3vq7"},{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"ha-mcp","purl":"pkg:pypi/ha-mcp","source":"PYSEC-2026-2507"}],"prev":{"headline":"SiYuan has a Full-Read SSRF via /api/network/forwardProxy","id":"CVE-2026-32110"},"products":["ha-mcp"],"published":"2026-03-11","related":[{"cvss_score":6.8,"headline":"ha-mcp has XSS via Unescaped HTML in OAuth Consent Form","id":"CVE-2026-32112","kev_date_added":null,"published":"2026-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["homeassistant-ai"]},"summary":"An unauthenticated attacker can perform internal network reconnaissance via an error oracle in the beta OAuth consent form of the Home Assistant MCP Server.","url":"https://insights.sbomify.com/CVE-2026-32111/"}