{"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-32112 in the wild and no public exploit code.","fix":"Upgrade ha-mcp to 7.0.0 or later.","what":"CVE-2026-32112 is a medium-severity cross-site scripting vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32112 and fix it if it is affected.\n\nWhat it is: CVE-2026-32112 is a medium-severity cross-site scripting vulnerability in homeassistant-ai ha-mcp, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32112 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-32112/ (Markdown: https://insights.sbomify.com/CVE-2026-32112/index.md)","id":"CVE-2026-32112","markdown":"https://insights.sbomify.com/CVE-2026-32112/index.md","name":"CVE-2026-32112","record":{"aliases":["GHSA-pf93-j98v-25pv","PYSEC-2026-2508"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Home Assistant MCP Server","requires_auth":"none","summary":"An attacker can execute JavaScript in the operator's browser via XSS in the OAuth consent form if beta OAuth mode is enabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"home_assistant_mcp_server","vendor":"homeassistant-ai"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"ha-mcp is a Home Assistant MCP Server. Prior to 7.0.0, the ha-mcp OAuth consent form renders user-controlled parameters via Python f-strings with no HTML escaping. An attacker who can reach the OAuth endpoint and convince the server operator to follow a crafted authorization URL could execute JavaScript in the operator's browser. This affects only users running the beta OAuth mode (ha-mcp-oauth), which is not part of the standard setup and requires explicit configuration. 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 has XSS via Unescaped HTML in OAuth Consent Form","id":"CVE-2026-32112","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Discourse: Open redirect via `sso_destination_url` cookie in `enter`","id":"CVE-2026-32113"},"packages":[{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"ha-mcp","purl":null,"source":"GHSA-pf93-j98v-25pv"},{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"ha-mcp","purl":"pkg:pypi/ha-mcp","source":"GHSA-pf93-j98v-25pv"},{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"ha-mcp","purl":"pkg:pypi/ha-mcp","source":"PYSEC-2026-2508"}],"prev":{"headline":"ha-mcp OAuth 2.1 DCR mode enables network reconnaissance via an error oracle","id":"CVE-2026-32111"},"products":["ha-mcp"],"published":"2026-03-11","related":[{"cvss_score":5.3,"headline":"ha-mcp OAuth 2.1 DCR mode enables network reconnaissance via an error oracle","id":"CVE-2026-32111","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["homeassistant-ai"]},"summary":"An attacker can execute JavaScript in the operator's browser via XSS in the OAuth consent form if beta OAuth mode is enabled.","url":"https://insights.sbomify.com/CVE-2026-32112/"}