CVE-2025-27516

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

March 5, 2025

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit, github.
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2025/04/msg00045.html
generic Patch Available

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

https://lists.debian.org/debian-lts-announce/2025/04/msg00022.html
github Patch Available

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

Vendor Advisories for CVE-2025-27516(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
py3-jinja2—3.1.6-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jinja22.11.3-1, 2.11.3-1+deb11u1, 2.11.3-1+deb11u22.11.3-1+deb11u3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jinja23.1.2-1, 3.1.2-1+deb12u1, 3.1.2-1+deb12u23.1.2-1+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jinja2—3.1.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jinja2—3.1.6-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
jinja22.0 ... 3.1.5 (51 versions)3.1.6—

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 132 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-27516?
CVE-2025-27516 is a high vulnerability 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 CVE-2025-27516 disclosed?
CVE-2025-27516 was first published in the National Vulnerability Database on March 5, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-27516 actively exploited?
CVE-2025-27516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.4% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-27516, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs