External risk intelligence

Home Assistant Core Unauthenticated Arbitrary File Write Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-64825

Home Assistant is commonly deployed as a network-accessible service to facilitate remote management and interaction with smart home devices. While the vulnerability occurs during initial onboarding, the product's primary role as a central, network-exposed hub for home automation makes it a likely target for internet-reachable deployment patterns.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability in Home Assistant Core that could allow unauthenticated attackers to write arbitrary files to any directory on the host system. The exploit occurs during the initial setup process by uploading a crafted backup archive, manipulating a field to bypass security checks and gain unauthorized write access. The main concern is to confirm if this technology is in use and assess any potential exposure.

  • Attackers write files anywhere on the system.
  • Home Assistant is a central, networked smart home hub.
  • Confirm use and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can compromise a Home Assistant instance during its initial setup by uploading a specially crafted backup archive. This archive manipulates a file path within the backup, allowing the attacker to bypass the intended backup directory and write arbitrary files to any location on the host system. If the Home Assistant process has root privileges, this can lead to full control over the host.

  • Unauthenticated network access required.
  • Triggered by uploading a malicious backup archive.
  • Enables arbitrary file write with root access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to write arbitrary files to any directory on the host filesystem. This is possible when the Home Assistant instance is undergoing initial onboarding and an attacker can upload a specially crafted backup archive. The attack manipulates a file within the archive to specify an absolute path, bypassing the intended backup directory and enabling the attacker to write content to any location on the filesystem, potentially leading to full system compromise if the process runs with root privileges.

  • Host filesystem data and configuration.
  • Crafted backup archive upload during onboarding.
  • Arbitrary file write, potential system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Home Assistant Core vulnerability impacts systems using the affected technology. Given its role as a network-accessible smart home hub, ownership likely falls to the platform or infrastructure team managing the Home Assistant deployment. The first practical step is to identify all instances of Home Assistant Core, assess their exposure and criticality, and confirm the accountable owner to plan remediation.

  • Platform or infrastructure teams own the issue.
  • Verify all Home Assistant Core instances.
  • Plan risk-based remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Home Assistant Core?

Home Assistant Core is the engine for a popular open-source smart home platform. It acts as a central hub, allowing users to automate, monitor, and manage various internet-connected devices, such as lights, thermostats, and security systems, from a single unified interface.

What does CVE-2026-64825 mean?

This CVE identifies a Path Traversal weakness (CWE-22). In plain terms, the software fails to properly validate a file path during a specific operation, allowing an attacker to 'break out' of the intended folder and save files anywhere on the host computer's storage.

How is this vulnerability triggered?

An attacker must upload a specially crafted backup archive specifically during the initial onboarding window of a Home Assistant instance. If the system is already set up and configured, uploading an archive under normal operational conditions does not trigger this path traversal vulnerability.

Is my Home Assistant instance at risk?

According to Halo Surface Signal, because Home Assistant is frequently deployed as a network-accessible service to enable remote control of smart devices, it is a likely candidate for internet-reachable deployment. If your instance is exposed to the internet, it is at higher risk.

What should I do to address this?

First, identify all instances of Home Assistant Core running in your environment. Confirm which versions are deployed to determine if they require updates. If you have any instances undergoing initial onboarding or deployment, ensure they are protected until you have verified the software is updated to the patched version.

References