Skip to main content
VulnerabilityPublished

CVE-2026-53453: ha-china blueprint-studio · Missing Authorization

Affects ha-china blueprint-studioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 2.5.2 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade blueprint-studio and ha-china/blueprint-studio to 2.5.2.

Affected software

ProductAffectedFixed in
ha-chinablueprint-studioAffected
  • <2.5.2
Fixed in
  • 2.5.2
GitHubha-china/blueprint-studiopkg:github/ha-china/blueprint-studioOther threatsAffected
  • <2.5.2
Fixed in
  • 2.5.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Blueprint Studio version 2.5.2. Users should upgrade to version 2.5.2 or later to remediate this issue. No additional mitigation steps are required once the upgrade is applied.

Description

Blueprint Studio, a VS Code-like editor for Home Assistant configuration files, had a missing authorization vulnerability prior to version 2.5.2. This flaw allowed any authenticated Home Assistant user, not just administrators, to access backend API actions intended for admins only. Exploitable surfaces included APIs for uploading, streaming, terminal WebSocket, service calls, template rendering, file access, and more. A non-admin user could perform unauthorized actions such as invoking arbitrary services, modifying configuration files, and accessing sensitive data, potentially compromising the confidentiality, integrity, and availability of the Home Assistant installation. The issue is fixed in version 2.5.2.

References

Community reviews

Loading reviews…