Skip to content

← Public intelligence

PyPI package

homeassistant-cli

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.6PyPIAmendedPublished

    Home Assistant Command-line Interface: Handling of user-supplied Jinja2 templates

    CVE-2026-40602 · GHSA-33qf-q99x-wpm8

    Affected
    • PyPI homeassistant-cli < 1.0.0
    Fixed in
    1.0.0· Vendor fix available
    Issue
    Impact Up to 1.0.0 of home-assitant-cli (or hass-cli for short) an unrestricted environment was used to handle Jninja2 templates instead of a sandboxed one. The user-supplied input within Jinja2 templates was rendered locally with no restrictions. This gave users access to Python's internals and extended the scope of templating beyond the intended usage. E. g., it was possible to render a template with hass-cli template bad-template.j2 --local that contained entries like or other malicious Jinja2 expressions. This can lead to arbitrary code execution on the local machine. In a two step process an adversary could trick/convince an user to download third-party templates which contain harmful code (e. g., perform data manipulation or establish a remote shell) then to render those templates unchecked/reviewed/verified with --local. The issue only affect the local machine and not a remote Home Assistant instance. It also requires user interventions. Patches 1.0.0 uses…

    Recommended action: Upgrade to 1.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →