Security readout for executives and security teams
Plain-English summary
A malicious backup can escape Home Assistant’s restore directory and overwrite files elsewhere on the host. In the official Docker image, Home Assistant runs as root, so a successful overwrite can lead to full code execution and compromise connected automation systems.
Executive priority
Prioritize remediation immediately, especially for official Docker deployments and systems accessible by multiple administrators. Compromise could affect confidentiality, integrity, availability, and connected physical automations. Investigate any recent restoration of untrusted backups.
Technical view
Before 2026.7.0, backup restoration follows crafted symbolic links whose targets are absolute paths outside the extraction directory. A subsequent archive member can write through that link. Overwriting automatically loaded Python files or custom components can produce code execution. The supplied CVSS 4.0 score is 9.3, with high privileges and user interaction required.
Likely exposure
Home Assistant Core versions earlier than 2026.7.0 are affected. Exposure is most serious for the official Docker image because the process runs as root. The CVSS vector indicates exploitation requires high privileges and user interaction, limiting unauthenticated exposure but making malicious or untrusted backup restoration particularly dangerous.
Exploitation context
The bundle includes an exploit-tagged reference but does not establish active exploitation. The CVE is not listed as KEV in the supplied data. Treat crafted backup archives as a credible attack path without claiming observed in-the-wild activity.
Researcher notes
The core weakness is CWE-22 caused by unsafe handling of tar symbolic-link entries during restoration. The described chain pairs a benign member name with an absolute link target, then writes through it. Source evidence supports the root-context Docker impact and code-execution consequence, but not active exploitation.
Mitigation direction
- Upgrade Home Assistant Core to version 2026.7.0 or later.
- Do not restore backups from untrusted or unverifiable sources.
- Restrict backup restoration privileges to trusted administrators.
- Follow Home Assistant guidance for any additional remediation or integrity checks.
Validation and detection
- Confirm every Home Assistant Core deployment reports version 2026.7.0 or later.
- Identify official Docker deployments and document their elevated impact.
- Review backup-restore activity for unexpected archives or administrator actions.
- Inspect auto-loaded Python paths and custom components for unexpected changes.
- Verify restored archives cannot write outside their designated extraction directory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-64824 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H1.76VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Release NotesCVE reference, VulnCheck · release-notes
- Pull RequestCVE reference, VulnCheck · issue-tracking
- Patch CommitCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/home-assistant-core-symlink-path-traversal-rce-via-backup-restoreCVE reference, VulnCheck · third-party-advisory
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-78r8-wwqv-r299CVE reference, CISA-ADP · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.