CVE-2026-64824
Path traversal in Home Assistant backup restore enables remote code execution.
Is CVE-2026-64824 being exploited?
Not confirmed. CVE-2026-64824 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.80% probability of exploitation in the next 30 days.
How severe is CVE-2026-64824?
CVE-2026-64824 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64824?
Yes. A fix has been recorded for CVE-2026-64824. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64824 affect?
CVE-2026-64824 affects Home Assistant Core < 2026.7.0, Home Assistant official Docker image, Systems running Home Assistant as root. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64824?
Upgrade to Home Assistant 2026.7.0+, avoid restoring untrusted backups, run service non-root
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted TAR with symlink during restore can write arbitrary absolute files, enabling remote code execution by overwriting Python import paths; official Docker runs as root.
Immediate action required
- affected< 2026.7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.