Loading vulnerability…
CVE-2026-64824 is a path traversal vulnerability in the backup-restore function of Home Assistant Core. A malicious backup archive can include a tar SYMTYPE entry whose member name appears benign but whose link target is an absolute path outside the intended extraction directory. When restore processing later writes a regular file through that unvalidated symlink, Home Assistant can be induced to write attacker-controlled content to arbitrary filesystem locations. In deployments using the official Docker image, where the Home Assistant process runs as root, this arbitrary file write can be escalated to remote code execution by overwriting Python files that are automatically imported at startup or by replacing code in custom component directories. Affected versions are Home Assistant Core before 2026.6.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone Python PoC exploit set for CVE-2026-64824 affecting Home Assistant Core backup restore. It is not part of a larger exploit framework. The main file, CVE-2026-64824.py, both modifies a legitimate Home Assistant backup and performs the authenticated upload step against the Home Assistant backup API. The exploit abuses a symlink path traversal in backup restoration: a crafted inner homeassistant.tar(.gz) contains a symlink entry such as data/evil_link pointing to an absolute path outside the extraction directory, followed by data/evil_link/sitecustomize.py. During restore, Home Assistant extracts the archive without validating symlink link targets, causing sitecustomize.py to be written into Python site-packages. On the next Python startup, sitecustomize.py is auto-imported, yielding code execution as root. Repository structure: README.md documents the vulnerability, exploitation chain, affected/fixed versions, and usage. CVE-2026-64824.py is the primary exploit entry point: it injects the malicious symlink and payload into an existing backup, can optionally build-only, uploads the archive to /api/backup/upload?agent_id=backup.local using a Bearer token, and prints instructions for the websocket restore command backup/restore. The websocket restore step is not fully implemented in Python and instead left as a manual/incomplete step. build_backup.py is a helper that creates a malicious backup archive from scratch in Home Assistant v2 backup format. inject_backup.py is a helper that injects the malicious entries into an existing real backup. All code is Python. Main exploit capabilities: create or modify Home Assistant backup tar archives; embed a symlink plus sitecustomize.py payload; upload the malicious backup to a target Home Assistant instance; facilitate restore-triggered persistence/execution. The included payload is basic and hardcoded: it runs 'id > /tmp/HA_PWNED_64824' via subprocess.Popen, serving as proof of root RCE. Because the payload is fixed and the restore trigger is only partially automated, the exploit is best classified as OPERATIONAL rather than weaponized.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.