Home Assistant Core before 2026.7.0 contains a path traversal vulnerability in the backup-restore function that allows attackers to write files to arbitrary absolute filesystem paths by supplying a crafted tar archive with a SYMTYPE entry containing a benign member name paired with an absolute linkname pointing outside the extraction directory. Because the official Docker image runs the Home Assistant process as root and the subsequent regular-file entry is written through the unvalidated symlink, attackers can achieve remote code execution by overwriting auto-imported Python paths such as site-packages/sitecustomize.py or custom component directories.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Public exploits 1
- Boreas37/CVE-2026-64824-PoC PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Change history 1
- First seenCVSS 9.3NVD modified 2026-10-24 19:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/home-assistant/core/commit/1e457600f1093c15e1325742d03e2b76498c79c1
- https://github.com/home-assistant/core/pull/172252
- https://github.com/home-assistant/core/releases/tag/2026.7.0
- https://www.vulncheck.com/advisories/home-assistant-core-symlink-path-traversal-rce-via-backup-restore
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-78r8-wwqv-r299