Home Assistant Core vulnerabilities

Home Assistant Core before version 2026.6.0 contains a path traversal vulnerability that allows unauthenticated attackers to write arbitrary files to any directory on the host filesystem by uploading a crafted backup archive during the initial onboarding window. Attackers can manipulate the 'name' field inside the uploaded archive's backup.json to supply an absolute path, causing pathlib.Path.__truediv__ to discard the configured backup directory prefix and write attacker-controlled content to arbitrary locations, with full filesystem access when the process runs as root.

A path traversal vulnerability in the backup-restore function of Home Assistant Core before 2026.7.0 allows attackers to write files to arbitrary absolute filesystem paths by supplying a crafted tar archive with a SYMTYPE entry. Because the official Docker image runs the process as root, attackers can achieve remote code execution by overwriting auto-imported Python paths such as site-packages/sitecustomize.py.

Home Assistant Core before 2026.5.4 contains a cross-site scripting vulnerability in the Shelly integration's `async_get_media_image()` method. Attackers controlling a Shelly device's thumb field can serve arbitrary HTML content via a data URI with `text/html` content type without validation against an image-only allowlist. This enables theft of session tokens and authenticated calls to sensitive endpoints like locks, alarms, and covers.

Home Assistant Core before v2025.8.0 is vulnerable to Directory Traversal. The Downloader integration does not fully validate file paths during concatenation, leaving a path traversal vulnerability.