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

Advisory record · `GHSA-33qf-q99x-wpm8`

- **Identifiers:** `GHSA-33qf-q99x-wpm8` · `CVE-2026-40602` · `PYSEC-2026-2518`
- **State:** Confirmed
- **Severity:** CVSS 5.6 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html) · [CWE-1336](https://cwe.mitre.org/data/definitions/1336.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 16 Apr 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Apr 2026, 21:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `homeassistant-cli` (PyPI): affected `<1.0.0`; fixed in `1.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Home Assistant Command-line Interface (homeassistant-cli) versions before 1.0.0 render user-supplied Jinja2 templates locally in an unrestricted environment rather than a sandboxed one. A user who is tricked into downloading a malicious template and rendering it with the local option can run arbitrary code on their own machine; the issue does not affect remote Home Assistant instances. Upgrade to 1.0.0, which uses a sandboxed environment. Until then, review templates before rendering them.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.6 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0010, the 1st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:03 UTC: First seen by agentprime
- 31 Oct 2026, 15:03 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-33qf-q99x-wpm8)

## Sources

- [GitHub Advisory Database: GHSA-33qf-q99x-wpm8](https://github.com/advisories/GHSA-33qf-q99x-wpm8)
- [OSV: GHSA-33qf-q99x-wpm8](https://osv.dev/vulnerability/GHSA-33qf-q99x-wpm8)
- <https://github.com/home-assistant-ecosystem/home-assistant-cli/security/advisories/GHSA-33qf-q99x-wpm8>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40602>
- <https://github.com/home-assistant-ecosystem/home-assistant-cli/pull/453>
- <https://github.com/home-assistant-ecosystem/home-assistant-cli>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-33qf-q99x-wpm8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-33qf-q99x-wpm8/>. Everything for agents: <https://agentprime.io/llms.txt>.