# Jinja has a sandbox breakout through indirect reference to format method

Advisory record · `GHSA-q2x7-8rv6-6q7h`

- **Identifiers:** `GHSA-q2x7-8rv6-6q7h` · `CVE-2024-56326` · `PYSEC-2026-1475`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html) · [CWE-1336](https://cwe.mitre.org/data/definitions/1336.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) · [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md)
- **Published:** 23 Dec 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Dec 2024, 17:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `jinja2` (PyPI): affected `<3.1.5`; fixed in `3.1.5`

## Machine-written summary

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

> Jinja2 versions before 3.1.5 are vulnerable to a sandbox breakout in the Jinja sandboxed environment, which fails to detect indirect calls to the str.format method. An attacker who can control the content of a template can store a reference to a malicious string's format method and pass it to a filter that calls it, executing arbitrary Python code; this requires custom filters, since none are built into Jinja. Upgrade jinja2 to version 3.1.5 or later.

Written 5 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.4 Medium, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0052, the 44th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 21 Dec 2024, 18:31 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/pallets/jinja/security/advisories/GHSA-q2x7-8rv6-6q7h)
- 31 Oct 2026, 14:35 UTC: First seen by agentprime
- 31 Oct 2026, 14:35 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q2x7-8rv6-6q7h)

## Sources

- [GitHub Advisory Database: GHSA-q2x7-8rv6-6q7h](https://github.com/advisories/GHSA-q2x7-8rv6-6q7h)
- [OSV: GHSA-q2x7-8rv6-6q7h](https://osv.dev/vulnerability/GHSA-q2x7-8rv6-6q7h)
- <https://github.com/pallets/jinja/security/advisories/GHSA-q2x7-8rv6-6q7h>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-56326>
- <https://github.com/pallets/jinja/commit/48b0687e05a5466a91cd5812d604fa37ad0943b4>
- <https://github.com/pallets/jinja>
- <https://github.com/pallets/jinja/releases/tag/3.1.5>
- <https://lists.debian.org/debian-lts-announce/2025/04/msg00022.html>

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-q2x7-8rv6-6q7h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q2x7-8rv6-6q7h/>. Everything for agents: <https://agentprime.io/llms.txt>.