CVE-2026-53456: Blueprint Studio terminal SSH private key written to disk
Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio terminal SSH key authentication in customcomponents/blueprintstudio/backend/terminalmanager.py wrote SSH private-key material to a file under the Home Assistant configuration directory before applying restrictive permissions and relied on best-effort cleanup. The key could temporarily remain on disk and could persist if cleanup failed or Home Assistant crashed. A user or process with filesystem access to the Home Assistant configuration directory could obtain the residual private key. This issue is fixed in version 2.5.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Blueprint Studioto a version that resolves this vulnerability.Fixed in 2.5.2
Event History
Frequently Asked Questions
Who is exposed to this issue?
Systems running Blueprint Studio before 2.5.2 are affected when terminal SSH private-key authentication is used. Exploitation requires local filesystem access to the Home Assistant configuration directory by a user or process.
What access is required to obtain the key?
An attacker needs access to the Home Assistant configuration directory while the key file exists, or after it remains behind because cleanup failed or Home Assistant crashed. The residual file may contain the SSH private key used for terminal authentication.
What should I do if I cannot patch immediately?
Upgrade Blueprint Studio to version 2.5.2. If upgrading cannot happen immediately, restrict filesystem access to the Home Assistant configuration directory and inspect it for residual private-key files created by terminal SSH authentication.