CVE-2026-53454: CWE-522: Insufficiently Protected Credentials in ha-china blueprint-studio
Blueprint Studio, a VS Code-like editor for Home Assistant configuration files, prior to version 2.5.2, stored Git credentials in plaintext in the .git-credentials file due to configuring Git's credential.helper store. This caused usernames and access tokens to be persistently saved outside the intended secure storage, making them accessible to other users or processes with filesystem access. The issue was fixed in version 2.5.2.
AI Analysis
Technical Summary
CVE-2026-53454 describes an insufficient protection of credentials vulnerability (CWE-522) in ha-china's Blueprint Studio. Before version 2.5.2, Blueprint Studio configured Git's credential.helper to use the 'store' method, which saves credentials in plaintext in the .git-credentials file for the user running Home Assistant. This allowed persistent storage of usernames and access tokens outside Blueprint Studio's intended secure storage, potentially exposing them to other users or processes with access to the same filesystem context. The persistent configuration also affected subsequent Git operations beyond the initial Blueprint Studio action. The vulnerability is resolved in version 2.5.2.
Potential Impact
The vulnerability allows plaintext storage of sensitive Git credentials (usernames and access tokens) on the filesystem, which can be read by other users or processes with access to the same filesystem context. This exposure increases the risk of credential theft and unauthorized access to Git repositories. The persistent nature of the credential helper configuration means that later Git operations could also expose these credentials.
Mitigation Recommendations
Upgrade Blueprint Studio to version 2.5.2 or later, where this issue is fixed. No additional mitigation steps are required as the fix addresses the insecure credential storage behavior.
CVE-2026-53454: CWE-522: Insufficiently Protected Credentials in ha-china blueprint-studio
Description
Blueprint Studio, a VS Code-like editor for Home Assistant configuration files, prior to version 2.5.2, stored Git credentials in plaintext in the .git-credentials file due to configuring Git's credential.helper store. This caused usernames and access tokens to be persistently saved outside the intended secure storage, making them accessible to other users or processes with filesystem access. The issue was fixed in version 2.5.2.
CVSS v4.0
Score 6.9medium
Affected software
ha-china
blueprint-studio
pkg:github/ha-china/blueprint-studioRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53454 describes an insufficient protection of credentials vulnerability (CWE-522) in ha-china's Blueprint Studio. Before version 2.5.2, Blueprint Studio configured Git's credential.helper to use the 'store' method, which saves credentials in plaintext in the .git-credentials file for the user running Home Assistant. This allowed persistent storage of usernames and access tokens outside Blueprint Studio's intended secure storage, potentially exposing them to other users or processes with access to the same filesystem context. The persistent configuration also affected subsequent Git operations beyond the initial Blueprint Studio action. The vulnerability is resolved in version 2.5.2.
Potential Impact
The vulnerability allows plaintext storage of sensitive Git credentials (usernames and access tokens) on the filesystem, which can be read by other users or processes with access to the same filesystem context. This exposure increases the risk of credential theft and unauthorized access to Git repositories. The persistent nature of the credential helper configuration means that later Git operations could also expose these credentials.
Mitigation Recommendations
Upgrade Blueprint Studio to version 2.5.2 or later, where this issue is fixed. No additional mitigation steps are required as the fix addresses the insecure credential storage behavior.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T16:31:21.494Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a84ca1cc6e8be0332c0b1ca
Added to database: 08/18/2026, 21:09:48 UTC
Last enriched: 09/11/2026, 14:19:51 UTC
Last updated: 10/03/2026, 14:46:08 UTC
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.