CVE-2025-27516

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 5, 2025

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit, github.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4126-2] jinja2 regression update

https://lists.debian.org/debian-lts-announce/2025/04/msg00045.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4126-1] jinja2 security update

https://lists.debian.org/debian-lts-announce/2025/04/msg00022.html
GitHub advisoryMentions a patch (unverified)

Sandbox breakout through attr filter selecting format method · Advisory · pallets/jinja · GitHub

https://github.com/pallets/jinja/security/advisories/GHSA-cpwx-vrp4-4pq7
GitHub commit Patch Available

commit 90457bbf33b8 (pallets/jinja)

Patch available: pallets/jinja 3.1.6 (contains commit 90457bbf33b8)

https://github.com/pallets/jinja/commit/90457bbf33b8662926ae65cdde4c4c32e756e403

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-ansible-rhel9-operator:v4.16.0-202504251337.p0.g0719399.assembly.stream.el92025-05-15redhat
redhatpython-jinja2-0:3.1.6-1.el10_02025-05-13redhat
redhatopenshift4/ose-olm-operator-controller-rhel9:v4.17.0-202504281009.p0.g8bc0220.assembly.stream.el92025-05-09redhat
redhatopenshift4/ose-ansible-operator:v4.12.0-202504071758.p0.g0bd975e.assembly.stream.el82025-05-08redhat
redhatopenshift4/ose-ansible-rhel9-operator:v4.17.0-202504231305.p0.gc649d73.assembly.stream.el92025-04-30redhat
redhatopenshift4/ose-ansible-rhel9-operator:v4.18.0-202504160934.p0.gb276665.assembly.stream.el92025-04-22redhat
redhatopenshift4/ose-ansible-operator:v4.13.0-202503310300.p0.g01bfabb.assembly.stream.el82025-04-17redhat
redhatopenshift4/ose-olm-operator-controller-rhel9:v4.18.0-202504090803.p0.gd1ac0f8.assembly.stream.el92025-04-16redhat
redhatopenshift4/ose-ansible-operator:v4.15.0-202503310336.p0.g52fc4b9.assembly.stream.el82025-04-16redhat
redhatopenshift4/ose-ansible-operator:v4.14.0-202503310335.p0.g0ad973f.assembly.stream.el82025-04-09redhat
redhatpython-jinja2-0:2.10.1-2.el8_2.42025-04-08redhat
redhatpython-jinja2-0:2.10.1-4.el8_6.22025-04-07redhat
redhatpython-jinja2-0:2.11.3-5.el9_22025-04-03redhat
redhatrhdh/rhdh-hub-rhel9:1.4.3-17436524612025-04-03redhat
redhatpython-jinja2-0:2.10.1-2.el8_4.22025-04-03redhat
redhatpython-jinja2-0:2.11.3-7.el9_42025-04-03redhat
redhatpython-jinja2-0:2.10.1-5.el8_82025-04-03redhat
redhatpython-jinja2-0:2.11.3-5.el9_02025-04-03redhat
redhatpython-jinja2-0:2.10.1-7.el8_102025-03-31redhat
redhatpython-jinja2-0:2.11.3-8.el9_52025-03-31redhat
redhatrhdh/rhdh-hub-rhel9:1.52025-03-27redhat
redhatopenstack-ansible-core-0:2.14.2-4.7.el9ost2025-03-27redhat
redhatpython3.11-jinja2-0:3.1.6-1.el9ap2025-03-25redhat
redhatansible-automation-platform-25/lightspeed-rhel8:2.5.250318-22025-03-25redhat
redhatansible-automation-platform-24/lightspeed-rhel8:2.4.250225-52025-03-24redhat
redhatpython-jinja2-0:3.1.6-1.el9ap2025-03-24redhat
redhatfence-agents-0:4.10.0-76.el9_5.62025-03-24redhat
redhatfence-agents-0:4.10.0-43.el9_2.122025-03-24redhat
redhatfence-agents-0:4.10.0-20.el9_0.212025-03-18redhat
redhatfence-agents-0:4.10.0-62.el9_4.112025-03-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 12 ecosystems)
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-jinja2—
  • every version up to 3.1.6-r0: fixed in 3.1.6-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jinja22.11.3-1, 2.11.3-1+deb11u1, 2.11.3-1+deb11u2
  • every version up to 2.11.3-1+deb11u3: fixed in 2.11.3-1+deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jinja23.1.2-1, 3.1.2-1+deb12u1, 3.1.2-1+deb12u2
  • every version up to 3.1.2-1+deb12u3: fixed in 3.1.2-1+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jinja2—
  • every version up to 3.1.6-1: fixed in 3.1.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jinja2—
  • every version up to 3.1.6-1: fixed in 3.1.6-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jinja22.0 ... 3.1.5 (51 versions)
  • every version up to 3.1.6: fixed in 3.1.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 166 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 77 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-12 17:14 UTCEG score recompute
  5. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-11 20:46 UTCEG score recompute
  7. 2026-10-11 18:57 UTCEG score recompute
  8. 2026-10-11 15:34 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-02 21:10 UTCOSV refresh
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 64 more
  1. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-09-13 18:39 UTCOSV refresh
  7. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-08-25 20:09 UTCOSV refresh
  24. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-08-09 12:07 UTCOSV refresh
  39. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  47. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  48. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  49. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  50. 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  51. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  52. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  53. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-07-24 13:11 UTCOSV refresh
  55. 2026-07-23 02:52 UTCEG score recompute
  56. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  57. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  58. 2026-07-20 17:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  59. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  60. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  61. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  62. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  63. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  64. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile

Frequently asked(5)

What is CVE-2025-27516?
CVE-2025-27516 is a high-severity vulnerability; its CVE record was published on March 5, 2025. 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…
When was the CVE record for CVE-2025-27516 published?
The CVE record for CVE-2025-27516 was published on March 5, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2025-27516 actively exploited?
CVE-2025-27516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-27516?
CVE-2025-27516 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-27516?
A fix for CVE-2025-27516 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-27516 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-27516

Explore →

Is Your Infrastructure Affected by CVE-2025-27516?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.