CVE-2026-53456

Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio terminal SSH key authentication in custom_components/blueprint_studio/backend/terminal_manager.py wrote SSH private-key material to a file under the Home Assistant configuration directory before applying restrictive permissions and relied on best-effort cleanup. The key could temporarily remain on disk and could persist if cleanup failed or Home Assistant crashed. A user or process with filesystem access to the Home Assistant configuration directory could obtain the residual private key. This issue is fixed in version 2.5.2.

CVSS

No CVSS.

References

Link	Resource
https://github.com/ha-china/blueprint-studio/commit/943aed0be67f3a910b0f70a3864288d5e17e55ce
https://github.com/ha-china/blueprint-studio/releases/tag/v2.5.2
https://github.com/ha-china/blueprint-studio/security/advisories/GHSA-3vg8-xf27-7q45

Configurations

No configuration.

History

22 Oct 2026, 22:10

Type	Values Removed	Values Added
Summary		(es) Blueprint Studio es un editor de archivos similar a VS Code para archivos de configuración de Home Assistant. Antes de la versión 2.5.2, la autenticación de clave SSH del terminal de Blueprint Studio en custom_components/blueprint_studio/backend/terminal_manager.py escribía material de clave privada SSH en un archivo bajo el directorio de configuración de Home Assistant antes de aplicar permisos restrictivos y dependía de una limpieza de mejor esfuerzo. La clave podía permanecer temporalmente en el disco y podía persistir si la limpieza fallaba o Home Assistant se bloqueaba. Un usuario o proceso con acceso al sistema de archivos al directorio de configuración de Home Assistant podía obtener la clave privada residual. Este problema está solucionado en la versión 2.5.2.

Information

Published : 2026-08-18 21:16

Updated : 2026-10-22 22:10

NVD link : CVE-2026-53456

Mitre link : CVE-2026-53456

CVE.ORG link : CVE-2026-53456

JSON object : View

Products Affected

No product.

CWE

CWE-522

Insufficiently Protected Credentials

{"id": "CVE-2026-53456", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-53456", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-19T18:03:49.705480Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.6, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "HIGH", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "ha-china", "product": "blueprint-studio", "versions": [{"status": "affected", "version": "< 2.5.2"}]}]}], "published": "2026-08-18T21:16:35.423", "references": [{"url": "https://github.com/ha-china/blueprint-studio/commit/943aed0be67f3a910b0f70a3864288d5e17e55ce", "source": "security-advisories@github.com"}, {"url": "https://github.com/ha-china/blueprint-studio/releases/tag/v2.5.2", "source": "security-advisories@github.com"}, {"url": "https://github.com/ha-china/blueprint-studio/security/advisories/GHSA-3vg8-xf27-7q45", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-522"}]}], "descriptions": [{"lang": "en", "value": "Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, Blueprint Studio terminal SSH key authentication in custom_components/blueprint_studio/backend/terminal_manager.py wrote SSH private-key material to a file under the Home Assistant configuration directory before applying restrictive permissions and relied on best-effort cleanup. The key could temporarily remain on disk and could persist if cleanup failed or Home Assistant crashed. A user or process with filesystem access to the Home Assistant configuration directory could obtain the residual private key. This issue is fixed in version 2.5.2."}, {"lang": "es", "value": "Blueprint Studio es un editor de archivos similar a VS Code para archivos de configuraci\u00f3n de Home Assistant. Antes de la versi\u00f3n 2.5.2, la autenticaci\u00f3n de clave SSH del terminal de Blueprint Studio en custom_components/blueprint_studio/backend/terminal_manager.py escrib\u00eda material de clave privada SSH en un archivo bajo el directorio de configuraci\u00f3n de Home Assistant antes de aplicar permisos restrictivos y depend\u00eda de una limpieza de mejor esfuerzo. La clave pod\u00eda permanecer temporalmente en el disco y pod\u00eda persistir si la limpieza fallaba o Home Assistant se bloqueaba. Un usuario o proceso con acceso al sistema de archivos al directorio de configuraci\u00f3n de Home Assistant pod\u00eda obtener la clave privada residual. Este problema est\u00e1 solucionado en la versi\u00f3n 2.5.2."}], "lastModified": "2026-10-22T22:10:00.250", "sourceIdentifier": "security-advisories@github.com"}