Answer in brief
CVE-2025-27516 records a Medium severity vulnerability in Jinja2 vulnerable to sandbox breakout through attr filter selecting format method. The current sources do not mark it as known exploited. The current feed maps Jinja2 (pip), jinja2 (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Jinja2 (pip), jinja2 (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Jinja2pip | <=3.1.5 | 3.1.6 |
| jinja2pypi | <3.1.6 | 3.1.6 |
Published upstream
Mar 5, 2025
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 18, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
An oversight in how the Jinja sandboxed environment interacts with the `|attr` filter allows an attacker that controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the content of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates. Jinja's sandbox does catch calls to `str.format` and ensures they don't escape the sandbox. However, it's possible to use the `|attr` filter to get a reference to a string's plain format method, bypassing the sandbox. After the fix, the `|attr` filter no longer bypasses the environment's attribute lookup.
Quoted source text, attributed separately from HOL analysis.