CVE-2026-53456: ha-china blueprint-studio · Insufficiently Protected Credentials
Affects ha-china blueprint-studioSource CVE Database V5
Not known to be exploited · CVSS 5.6 Medium : upgrade to 2.5.2 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.2
CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade blueprint-studio and ha-china/blueprint-studio to 2.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ha-chinablueprint-studio | Affected
| Fixed in
|
GitHubha-china/blueprint-studiopkg:github/ha-china/blueprint-studioOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade blueprint-studio to version 2.5.2 or later, where the issue is fixed. No other mitigation is indicated or necessary once the update is applied.
Description
CVE-2026-53456 is a medium severity vulnerability in ha-china's blueprint-studio prior to version 2.5.2. The issue involves insufficient protection of SSH private key credentials used for terminal authentication. The private key was written to a file in the Home Assistant configuration directory with a best-effort cleanup approach, which could fail or be interrupted, leaving the key accessible on disk. This residual key could be accessed by any user or process with filesystem access to the configuration directory. The vulnerability is fixed in version 2.5.2.