Blueprint Studio stored Git credentials in plaintext Git credential store
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-522.
Summary
Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio configured Git's credential.helper store when saving Git credentials, causing Git credential-store to persist usernames and access tokens in plaintext in the .git-credentials file for the user running Home Assistant. Tokens could remain outside Blueprint Studio's intended Home Assistant storage and be read by other users or processes with access to the same filesystem context. The persistent helper configuration also affected later Git operations beyond the immediate Blueprint Studio action. This issue is fixed in version 2.5.2.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA blueprint-studio (ha-china) Fixed in 2.5.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-53454
References
More ha-china vulnerabilities
- TI-2026-38536 Blueprint Studio Git credential helper command injection CVSS 4.0HIGH 8.6
- TI-2026-38534 Blueprint Studio API authorization bypass for non-admin Home Assistant users CVSS 4.0HIGH 8.7
- TI-2026-38538 Blueprint Studio terminal command working directory not bounded to config directory CVSS 4.0MEDIUM 5.1
- TI-2026-38537 Blueprint Studio terminal SSH private key written to disk CVSS 4.0MEDIUM 5.6
- TI-2026-38539 Blueprint Studio API exposed internal exception details CVSS 4.0MEDIUM 5.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences