CVE-2025-27516
No exploitation reported by the sources we read.
- Published2025-03-05
- WeaknessCWE-1336
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Jinja is an extensible templating engine. Prior to 3.1.6, 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. This vulnerability is fixed in 3.1.6.
Timeline
dates in UTC- 2025-03-0521:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-27516?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-27516?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 11.0 | = 11.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.1 | < 3.1.6 | 3.1.6 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- python3-jinja2AlmaLinux:10all versions · fixed in 3.1.6-1.el10_0and 1 other package
- python3-jinja2AlmaLinux:9all versions · fixed in 2.11.3-8.el9_5
- python3-jinja2AlmaLinux:8all versions · fixed in 2.10.1-7.el8_10
Vendor advisories
Red Hat Bug Fix Advisory: Red Hat Quay v3.14.1 bug fix release
Red Hat Bug Fix Advisory: Red Hat Quay v3.13.5 bug fix release
Red Hat Bug Fix Advisory: Red Hat Quay v3.12.9 bug fix release
Red Hat Security Advisory: OpenShift Container Platform 4.18.9 bug fix and security update
Red Hat Bug Fix Advisory: Red Hat Quay v3.11.10 bug fix release
Red Hat Security Advisory: Red Hat Developer Hub 1.5.1 release.
Fix
- Vendor fix Red Hat Product Security RHBA-2025:7674 · 30 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Vendor fix Red Hat Product Security RHSA-2025:3775 · 4 productsFor OpenShift Container Platform 4.18 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
- Vendor fix Red Hat Product Security RHSA-2025:3374 · 1 productFor more about Red Hat Developer Hub, see References links
- Workaround from the vendor Red Hat Product Security RHBA-2025:7674 · 30 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Advisories and patches
- github.comPatch
- github.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CVSS 4.0 vector
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2025-03-05
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2025-27516?
Is CVE-2025-27516 actively exploited?
What is the CVSS score for CVE-2025-27516?
Running OpenShift Container Platform? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.