# CVE-2026-53456: Blueprint Studio terminal SSH private key written to disk

> An attacker with filesystem access can read residual SSH private keys written to disk by Blueprint Studio, potentially compromising SSH authentication.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-3vg8-xf27-7q45

## What is CVE-2026-53456?

CVE-2026-53456 is a medium-severity vulnerability in ha-china blueprint-studio, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 custom_components/blueprint_studio/backend/terminal_manager.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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-53456?


## How do I fix CVE-2026-53456?

No fix has been published for CVE-2026-53456 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53456 being exploited?

There is no known exploitation of CVE-2026-53456 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53456 and fix it if it is affected.

What it is: CVE-2026-53456 is a medium-severity vulnerability in ha-china blueprint-studio, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53456 in the wild and no public exploit code.

Affected product: ha-china blueprint-studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53456/ (Markdown: https://insights.sbomify.com/CVE-2026-53456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53456
- OSV: https://osv.dev/vulnerability/CVE-2026-53456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53456/
Summaries are generated and may contain mistakes; the official description above is the record.