CVE-2026-53455
Command injection in Blueprint Studio Git credential helper (pre-2.5.2).
Is CVE-2026-53455 being exploited?
Not confirmed. CVE-2026-53455 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-53455?
CVE-2026-53455 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53455?
Yes. A fix has been recorded for CVE-2026-53455. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53455 affect?
CVE-2026-53455 affects Home Assistant - Blueprint Studio (< 2.5.2), Home Assistant installations using custom_components/blueprint_studio. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53455?
Upgrade to Blueprint Studio 2.5.2; rotate Git credentials; audit Home Assistant configs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker who can set Git username/token can inject shell commands, achieving code execution as the Home Assistant user and read/modify configs.
Immediate action required
- affected< 2.5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.