# CVE-2026-53454: Blueprint Studio stored Git credentials in plaintext Git credential store

> Blueprint Studio stored Git credentials in plaintext, allowing local attackers to read access tokens from the filesystem.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-pgxq-h2pc-gqq8

## What is CVE-2026-53454?

CVE-2026-53454 is a medium-severity vulnerability in ha-china blueprint-studio, published on 18 Aug 2026. An attacker needs administrator access to exploit it, 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 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-53454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53454 is a medium-severity vulnerability in ha-china blueprint-studio, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53454 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-53454/ (Markdown: https://insights.sbomify.com/CVE-2026-53454/index.md)
```

## Sources

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

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