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, improperly configured Git's credential.helper store to persist Git credentials in plaintext in the .git-credentials file. This allowed usernames and access tokens to be stored outside of Blueprint Studio's 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 when saving Git credentials, causing usernames and access tokens to be saved in plaintext in the .git-credentials file of the user running Home Assistant. This persisted beyond the immediate Blueprint Studio operation, affecting subsequent Git commands and exposing credentials to other users or processes with access to the same filesystem context. The vulnerability is resolved in Blueprint Studio version 2.5.2.
Potential Impact
The vulnerability allows sensitive Git credentials, including usernames and access tokens, to be stored in plaintext on disk in a location accessible to other users or processes sharing the filesystem context. This exposure could lead to unauthorized access to Git repositories or other resources accessible via these credentials. The issue affects all operations using the persistent credential helper configuration until the software is updated.
Mitigation Recommendations
This vulnerability is fixed in Blueprint Studio version 2.5.2. Users should upgrade to version 2.5.2 or later to ensure Git credentials are properly protected. Patch status is not explicitly confirmed beyond this fix version; users should verify with the vendor advisory for current remediation guidance.
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, improperly configured Git's credential.helper store to persist Git credentials in plaintext in the .git-credentials file. This allowed usernames and access tokens to be stored outside of Blueprint Studio's 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
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 when saving Git credentials, causing usernames and access tokens to be saved in plaintext in the .git-credentials file of the user running Home Assistant. This persisted beyond the immediate Blueprint Studio operation, affecting subsequent Git commands and exposing credentials to other users or processes with access to the same filesystem context. The vulnerability is resolved in Blueprint Studio version 2.5.2.
Potential Impact
The vulnerability allows sensitive Git credentials, including usernames and access tokens, to be stored in plaintext on disk in a location accessible to other users or processes sharing the filesystem context. This exposure could lead to unauthorized access to Git repositories or other resources accessible via these credentials. The issue affects all operations using the persistent credential helper configuration until the software is updated.
Mitigation Recommendations
This vulnerability is fixed in Blueprint Studio version 2.5.2. Users should upgrade to version 2.5.2 or later to ensure Git credentials are properly protected. Patch status is not explicitly confirmed beyond this fix version; users should verify with the vendor advisory for current remediation guidance.
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
- Remediation Level
- null
Threat ID: 6a84ca1cc6e8be0332c0b1ca
Added to database: 08/18/2026, 21:09:48 UTC
Last enriched: 08/18/2026, 21:21:23 UTC
Last updated: 08/18/2026, 23:10:09 UTC
Views: 3
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.