Blueprint Studio API authorization bypass for non-admin Home Assistant users
Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio exposed administrator-intended backend API actions to any authenticated Home Assistant user because the backend did not consistently enforce the panel's admin-only authorization boundary. Affected surfaces included the backend API, upload API, stream routes, terminal WebSocket, Blueprint Studio WebSocket subscriptions, call_service, render_template, global_replace, file and stream access paths, upload handling, and terminal helpers. A non-admin user could invoke arbitrary Home Assistant services, expose Home Assistant state through templates, modify configuration files, access streamed or downloaded configuration content, upload files, or reach terminal-related helpers. These actions could compromise the confidentiality, integrity, and availability of the Home Assistant installation. This issue is fixed in version 2.5.2.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-53453
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 16:49 UTC · Revision 1
Source evidence
Blueprint Studio API authorization bypass for non-admin Home Assistant users
core-osv · Original sourcePublished 18 Aug 2026, 20:48 UTC
Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio exposed administrator-intended backend API actions to any authenticated Home Assistant user because the backend did not consistently enforce the panel's admin-only authorization boundary. Affected surfaces included the backend API, upload API, stream routes, terminal WebSocket, Blueprint Studio WebSocket subscriptions, call_service, render_template, global_replace, file and stream access paths, upload handling, and terminal helpers. A non-admin user could invoke arbitrary Home Assistant services, expose Home Assistant state through templates, modify configuration files, access streamed or downloaded configuration content, upload files, or reach terminal-related helpers. These actions could compromise the confidentiality, integrity, and availability of the Home Assistant installation. This issue is fixed in version 2.5.2.
osv:CVE-2026-53453
Complete source record
{
"id": "43f26221d7f3ac2871169177824614fea123ddd61edb0ed23acea12be7a4e6a7",
"url": "https://osv.dev/vulnerability/CVE-2026-53453",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Blueprint Studio API authorization bypass for non-admin Home Assistant users",
"summary": "Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio exposed administrator-intended backend API actions to any authenticated Home Assistant user because the backend did not consistently enforce the panel's admin-only authorization boundary. Affected surfaces included the backend API, upload API, stream routes, terminal WebSocket, Blueprint Studio WebSocket subscriptions, call_service, render_template, global_replace, file and stream access paths, upload handling, and terminal helpers. A non-admin user could invoke arbitrary Home Assistant services, expose Home Assistant state through templates, modify configuration files, access streamed or downloaded configuration content, upload files, or reach terminal-related helpers. These actions could compromise the confidentiality, integrity, and availability of the Home Assistant installation. This issue is fixed in version 2.5.2.",
"evidence": "osv:CVE-2026-53453",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-53453",
"aliases": [
"CVE-2026-53453",
"GHSA-ppwq-ch6x-936g"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/ha-china/blueprint-studio",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "943aed0be67f3a910b0f70a3864288d5e17e55ce"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2.5.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "943aed0be67f3a910b0f70a3864288d5e17e55ce"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "943aed0be67f3a910b0f70a3864288d5e17e55ce"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v2.5.2"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2.5.2"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v2.5.1",
"v2.5.0",
"v2.4.8",
"v2.4.7",
"v2.4.6",
"v2.4.4",
"v2.4.3",
"v2.4.2",
"v2.4.1",
"v2.4.0",
"v2.3.0",
"v2.2.2",
"v2.2.1",
"v2.2.0",
"v2.1.5",
"v2.1.4",
"v2.1.3",
"v2.1.2",
"v2.1.1",
"v2.1.0",
"v2.0.6",
"v2.0.5",
"v2.0.4",
"v2.0.3",
"v2.0.2",
"v2.0.1",
"v2.0.0",
"v1.5.2",
"v1.5.1",
"v1.5.0",
"v1.4.1",
"v1.4.0",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.1",
"v.1.2.0",
"v1.1.1",
"V1.1.0",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53453.json"
}
}
],
"modified": "2026-10-28T02:30:21.091503646Z",
"provider": "osv",
"references": [
"https://github.com/ha-china/blueprint-studio/releases/tag/v2.5.2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53453.json",
"https://github.com/ha-china/blueprint-studio/security/advisories/GHSA-ppwq-ch6x-936g",
"https://nvd.nist.gov/vuln/detail/CVE-2026-53453",
"https://github.com/ha-china/blueprint-studio/commit/943aed0be67f3a910b0f70a3864288d5e17e55ce"
],
"provider_metadata": {
"cwe_ids": [
"CWE-862"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53453.json"
}
},
"related_cves": [
{
"value": "CVE-2026-53453",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 487388,
"published_at": "2026-08-18T20:48:20.578+00:00"
}