CVE-2016-10745: Jinja2 - Sandbox Escape

jinja2 Updated 02 Oct 2025

Summary

10/04/2019
Yes i
High
8.6

CVE-2016-10745: Jinja2 sandbox escape vulnerability. Affects jinja2 versions < 2.8.1. Fixed in 2.8.1. How to fix ↓

Also tracked for

The same CVE-2016-10745 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Jinja2 is a popular templating engine for Python. It provides a powerful and flexible way to generate dynamic HTML, XML, or other markup formats. Jinja2 is widely used in web development frameworks and applications to separate the presentation layer from the business logic. However, Jinja2 versions before 2.8.1 are vulnerable to a high severity issue that allows a sandbox escape.

Vulnerability Detail

The vulnerability in Jinja2 (CVE-2016-10745) arises from a flaw in the str.format function. This function, when used in a sandboxed environment, can be exploited to break out of the sandbox and execute arbitrary code. An attacker with the ability to control the format string can craft a payload that bypasses the intended restrictions and gains unauthorized access to sensitive resources or performs malicious actions. This vulnerability has a CVSS score of 8.6, indicating a high severity level.

How To Fix

Latest published version: 3.1.6 as of 23 Oct 2026

pip install --upgrade "jinja2==3.1.6"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.8.1

This is the first release that contains the fix.

pip install --upgrade "jinja2==2.8.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to apply the recommended fix by upgrading to Jinja2 version 2.8.1 or later.

Conclusion

In conclusion, the Jinja2 vulnerability (CVE-2016-10745) allows a sandbox escape, enabling attackers to execute arbitrary code. It is crucial to upgrade to Jinja2 version 2.8.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for jinja2 →

Share this vulnerability

FAQ

Jinja2 is a templating engine for Python that allows developers to generate dynamic HTML, XML, or other markup formats. It is widely used in web development frameworks and applications.

This vulnerability allows an attacker to escape the sandbox and execute arbitrary code. It can lead to unauthorized access to sensitive resources or the execution of malicious actions.

The CVSS score of this vulnerability is 8.6, indicating a high severity level.

No, there is no known workaround for this vulnerability. It is essential to upgrade to Jinja2 version 2.8.1 or later.

To fix this vulnerability, you need to upgrade Jinja2 to version 2.8.1 or later. Make sure to update your dependencies and use the updated version in your projects.

Related vulnerabilities

Recent vulnerabilities recorded for jinja2.

How To Fix

Latest published version: 3.1.6 as of 23 Oct 2026

pip install --upgrade "jinja2==3.1.6"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.8.1

This is the first release that contains the fix.

pip install --upgrade "jinja2==2.8.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback