{"answers":{"affected":"3 open source packages ship an affected version, including homeassistant.","exploited":"There is no known exploitation of CVE-2026-64825 in the wild and no public exploit code.","fix":"Upgrade homeassistant to 2026.6.0 or later.","what":"CVE-2026-64825 is a critical path traversal vulnerability in home-assistant Home Assistant Core, published on 21 Jul 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-64825 and fix it if it is affected.\n\nWhat it is: CVE-2026-64825 is a critical path traversal vulnerability in home-assistant Home Assistant Core, published on 21 Jul 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-64825 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- homeassistant (PyPI): affected all versions; fixed in 2026.6.0\n- homeassistant (PyPI): affected all versions; fixed in 2026.6.0\n- homeassistant (PyPI): affected all versions; fixed in 2026.6.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-64825/ (Markdown: https://insights.sbomify.com/CVE-2026-64825/index.md)","id":"CVE-2026-64825","markdown":"https://insights.sbomify.com/CVE-2026-64825/index.md","name":"CVE-2026-64825","record":{"aliases":["GHSA-5hxg-r395-fqxx","PYSEC-2026-3669"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Home Assistant Core","requires_auth":"none","summary":"Unauthenticated attackers can write arbitrary files to the host filesystem via a crafted backup upload during onboarding, potentially achieving code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Home Assistant Core before 2026.6.0 contains a path traversal vulnerability that allows unauthenticated attackers to write arbitrary files to any directory on the host filesystem by uploading a crafted backup archive during the initial onboarding window. Attackers can manipulate the 'name' field inside the uploaded archive's backup.json to supply an absolute path, causing pathlib.Path.__truediv__ to discard the configured backup directory prefix and write attacker-controlled content to arbitrary locations, with full filesystem access when the process runs as root.","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":"Home Assistant Core \u003c 2026.6.0 Path Traversal File Write via Backup Upload","id":"CVE-2026-64825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"rConfig \u003c 8.2.13 Path Traversal File Read via FileDownloadController","id":"CVE-2026-64826"},"packages":[{"ecosystem":"PyPI","fixed":["2026.6.0"],"introduced":["0"],"last_affected":[],"package":"homeassistant","purl":null,"source":"GHSA-5hxg-r395-fqxx"},{"ecosystem":"PyPI","fixed":["2026.6.0"],"introduced":["0"],"last_affected":[],"package":"homeassistant","purl":"pkg:pypi/homeassistant","source":"GHSA-5hxg-r395-fqxx"},{"ecosystem":"PyPI","fixed":["2026.6.0"],"introduced":["0"],"last_affected":[],"package":"homeassistant","purl":"pkg:pypi/homeassistant","source":"PYSEC-2026-3669"}],"prev":{"headline":"Home Assistant Core \u003c 2026.7.0 Symlink Path Traversal RCE via backup-restore","id":"CVE-2026-64824"},"products":["Home Assistant Core"],"published":"2026-07-21","related":[],"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":"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-10-08","vendors":["home-assistant"]},"summary":"Unauthenticated attackers can write arbitrary files to the host filesystem via a crafted backup upload during onboarding, potentially achieving code execution.","url":"https://insights.sbomify.com/CVE-2026-64825/"}