# CVE-2026-53458: Blueprint Studio API exposed internal exception details

> Authenticated users can view internal exception details containing filesystem paths, aiding in fingerprinting the Home Assistant installation.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-6vc4-5wqj-fm6p

## What is CVE-2026-53458?

CVE-2026-53458 is a medium-severity vulnerability in ha-china blueprint-studio, published on 18 Aug 2026. Any signed-in user can exploit it over the network, 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 backend API handlers in custom_components/blueprint_studio/backend/api.py returned raw exception strings to authenticated Home Assistant users. Some exception messages could contain internal filesystem paths or implementation details. The disclosed information could help an authenticated user fingerprint a Home Assistant installation and refine follow-up attacks. This issue is fixed in version 2.5.2.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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


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

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

## Is CVE-2026-53458 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53458 is a medium-severity vulnerability in ha-china blueprint-studio, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53458 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-53458/ (Markdown: https://insights.sbomify.com/CVE-2026-53458/index.md)
```

## Sources

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

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