Path Traversal in homeassistant (CVE-2026-64825)
Summary
Path traversal in homeassistant (CVE-2026-64825). Data can be tampered with by attackers. Mitigation: upgrade to 2026.6.0 or later.
Original description
The description as published by the source.
Home Assistant Core before 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-64825 has been found in homeassistant.
Data can be tampered with by attackers. CVSS score: 9.3/10.
What to do: upgrade homeassistant to 2026.6.0 or later.
If unsure, ask your IT team or search "homeassistant CVE-2026-64825" on the vendor's site.
CVE-2026-64825 (homeassistant) — CWE-22 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2026.6.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in homeassistant.
Check the vendor advisory for the affected versions of homeassistant.
Severity: Critical (CVSS 9.3/10). Data can be tampered with by attackers.
Update to 2026.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'homeassistant' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'homeassistant' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
homeassistantを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade homeassistant to 2026.6.0ステージング環境で 2026.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web vulncheck.com