← Back to issue list

build(deps): update dependency jinja2 to v3.1.6 [security] (hotfix/7.5) - autoclosed

View original Github issue

Metadata

Project
snapcraft
Number
#5307
Type
pull request
State
closed
Author
renovate[bot]
Labels
β€”
Created
Updated
Closed

Current evaluation

Autoclosed unmerged as the hotfix/7.5 update aged out; Jinja2 3.1.6 later reached main through merged PR #5312 (8bc044979).

Resolution: closed stale

Reason: PR #5307 was auto-closed without reviews, CI checks, comments, or a merge commit as the 7.5 hotfix aged out. The dependency update was subsequently merged to main in PR #5312 at commit 8bc044979.

Evaluated by: mr-cal-bot

No scores available.

Issue body

This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [Jinja2](https://redirect.github.com/pallets/jinja) ([changelog](https://jinja.palletsprojects.com/changes/)) | `==3.1.4` -> `==3.1.6` | [![age](https://developer.mend.io/api/mc/badges/age/pypi/jinja2/3.1.6?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/pypi/jinja2/3.1.6?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/pypi/jinja2/3.1.4/3.1.6?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/jinja2/3.1.4/3.1.6?slim=true)](https://docs.renovatebot.com/merge-confidence/) | ### GitHub Vulnerability Alerts #### [CVE-2025-27516](https://redirect.github.com/pallets/jinja/security/advisories/GHSA-cpwx-vrp4-4pq7) 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. --- ### Release Notes <details> <summary>pallets/jinja (Jinja2)</summary> ### [`v3.1.6`](https://redirect.github.com/pallets/jinja/releases/tag/3.1.6) [Compare Source](https://redirect.github.com/pallets/jinja/compare/3.1.5...3.1.6) This is the Jinja 3.1.6 security release, which fixes security issues but does not otherwise change behavior and should not result in breaking changes compared to the latest feature release. PyPI: https://pypi.org/project/Jinja2/3.1.6/ Changes: https://jinja.palletsprojects.com/en/stable/changes/#version-3-1-6 - The `|attr` filter does not bypass the environment's attribute lookup, allowing the sandbox to apply its checks. https://github.com/pallets/jinja/security/advisories/GHSA-cpwx-vrp4-4pq7 ### [`v3.1.5`](https://redirect.github.com/pallets/jinja/blob/HEAD/CHANGES.rst#Version-315) [Compare Source](https://redirect.github.com/pallets/jinja/compare/3.1.4...3.1.5) Released 2024-12-21 - The sandboxed environment handles indirect calls to `str.format`, such as by passing a stored reference to a filter that calls its argument. :ghsa:`q2x7-8rv6-6q7h` - Escape template name before formatting it into error messages, to avoid issues with names that contain f-string syntax. :issue:`1792`, :ghsa:`gmj6-6f8f-6699` - Sandbox does not allow `clear` and `pop` on known mutable sequence types. :issue:`2032` - Calling sync `render` for an async template uses `asyncio.run`. :pr:`1952` - Avoid unclosed `auto_aiter` warnings. :pr:`1960` - Return an `aclose`-able `AsyncGenerator` from `Template.generate_async`. :pr:`1960` - Avoid leaving `root_render_func()` unclosed in `Template.generate_async`. :pr:`1960` - Avoid leaving async generators unclosed in blocks, includes and extends. :pr:`1960` - The runtime uses the correct `concat` function for the current environment when calling block references. :issue:`1701` - Make `|unique` async-aware, allowing it to be used after another async-aware filter. :issue:`1781` - `|int` filter handles `OverflowError` from scientific notation. :issue:`1921` - Make compiling deterministic for tuple unpacking in a `{% set ... %}` call. :issue:`2021` - Fix dunder protocol (`copy`/`pickle`/etc) interaction with `Undefined` objects. :issue:`2025` - Fix `copy`/`pickle` support for the internal `missing` object. :issue:`2027` - `Environment.overlay(enable_async)` is applied correctly. :pr:`2061` - The error message from `FileSystemLoader` includes the paths that were searched. :issue:`1661` - `PackageLoader` shows a clearer error message when the package does not contain the templates directory. :issue:`1705` - Improve annotations for methods returning copies. :pr:`1880` - `urlize` does not add `mailto:` to values like `@a@b`. :pr:`1870` - Tests decorated with `@pass_context`` can be used with the ``|select`` filter. :issue:`1624\` - Using `set` for multiple assignment (`a, b = 1, 2`) does not fail when the target is a namespace attribute. :issue:`1413` - Using `set` in all branches of `{% if %}{% elif %}{% else %}` blocks does not cause the variable to be considered initially undefined. :issue:`1253` </details> --- ### Configuration πŸ“… **Schedule**: Branch creation - "" in timezone Etc/UTC, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. β™» **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. πŸ”• **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/canonical/snapcraft). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xODUuNCIsInVwZGF0ZWRJblZlciI6IjM5LjE4NS40IiwidGFyZ2V0QnJhbmNoIjoiaG90Zml4LzcuNSIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha β€” closed stale Autoclosed unmerged as the hotfix/7.5 update aged out; Jinja2 3.1.6 later reached main through merged PR #5312 (8bc044979).
stealth/space-bunny-alpha β€” closed stale Renovate’s Jinja2 3.1.6 hotfix/7.5 bump was autoclosed unmerged without review or CI; #5312 later added 3.1.6 only to the Sphinx docs requirements.
stealth/space-bunny-alpha β€” closed stale Renovate's Jinja2 3.1.6 security update for hotfix/7.5 was autoclosed unmerged, with no reviews, CI checks, comments, or resolving commit recorded.
qwen/qwen3.6-35b-a3b β€” β€” The Jinja2 v3.1.6 security update was autoclosed without merging. The pull request received no reviews or CI checks and was automatically closed, leaving the dependency update unapplied.
qwen3.6-35b-a3b-mtp-q6 β€” β€” Jinja2 v3.1.6 security update PR was autoclosed without merging. Renovate automatically closed the request, likely due to branch deletion or staleness, leaving the dependency unupdated.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft#5312 (confidence 95%)

    Merged the Jinja2 3.1.6 bump for the Sphinx docs requirements in commit 8bc044979.

Related issues

Issue Project State Summary Similarity
#5191 build(deps): update dependency jinja2 to v3.1.5 [security] (hotfix/7.5) - autoclosed snapcraft closed Jinja2 3.1.5 hotfix/7.5 PR #5191 was autoclosed unmerged; the equivalent main-branch security update merged via #5190 in commit 98511dc44.
97%
#5192 build(deps): update dependency jinja2 to v3.1.5 [security] (hotfix/8.5) - autoclosed snapcraft closed Renovate autoclosed the unmerged hotfix/8.5 Jinja2 3.1.5 update; the equivalent main-branch update merged in #5190 at 98511dc44.
96%
#2066 build(deps): update dependency jinja2 to v3.1.5 [security] (hotfix/3.2) - autoclosed charmcraft closed Renovate autoclosed #2066 unmerged; the equivalent Jinja2 3.1.5 security update landed on main via #2064 (979176de).
96%
#2065 build(deps): update dependency jinja2 to v3.1.5 [security] (hotfix/2.7) - autoclosed charmcraft closed Renovate's Jinja2 3.1.5 hotfix/2.7 update was autoclosed unmerged; the equivalent main-branch update merged in #2064 via 979176de.
94%
#2209 build(deps): update dependency jinja2 to v3.1.6 [security] (hotfix/3.3) - autoclosed charmcraft closed Renovate's Jinja2 3.1.6 hotfix/3.3 update was autoclosed unmerged; dependency updates were later consolidated and merged in #2223 (e148af23).
93%
#2210 build(deps): update dependency jinja2 to v3.1.6 [security] (hotfix/3.4) - autoclosed charmcraft closed Jinja2 3.1.6 security bump for hotfix/3.4 was autoclosed unmerged, with no review, CI, comments, or resolving commit.
93%
#5306 build(deps): update dependency jinja2 to v3.1.6 [security] (main) - autoclosed snapcraft closed Autoclosed unmerged after the Jinja2 3.1.6 security update landed through #5305; #5312 separately updated docs requirements.
92%
#2207 build(deps): update dependency jinja2 to v3.1.6 [security] (main) - autoclosed charmcraft closed Jinja2 3.1.6 update was autoclosed unmerged; the same pin landed through #2223 in commit e148af23.
92%
#2208 build(deps): update dependency jinja2 to v3.1.6 [security] (hotfix/2.7) - autoclosed charmcraft closed Renovate's Jinja2 3.1.6 update for hotfix/2.7 was autoclosed unmerged with no review, CI, comments, or resolving commit.
92%
#5309 build(deps): update dependency jinja2 to v3.1.6 [security] (hotfix/8.7) - autoclosed snapcraft closed Renovate PR #5309 was autoclosed unmerged; Jinja2 3.1.6 reached Snapcraft 8.7.2 through merged hotfix PR #5311, backporting the update from #5305.
92%