Skip to content

[Snyk] Security upgrade jinja2 from 3.0.3 to 3.1.4#4

Open
StemmlerSisters wants to merge 2 commits into
mainfrom
snyk-fix-fc5ac6bf421a0d59907d0a8d44676c1e
Open

[Snyk] Security upgrade jinja2 from 3.0.3 to 3.1.4#4
StemmlerSisters wants to merge 2 commits into
mainfrom
snyk-fix-fc5ac6bf421a0d59907d0a8d44676c1e

Conversation

@StemmlerSisters

Copy link
Copy Markdown
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • requirements-dev.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 556/1000
Why? Recently disclosed, Has a fix available, CVSS 5.4
Cross-site Scripting (XSS)
SNYK-PYTHON-JINJA2-6809379
jinja2:
3.0.3 -> 3.1.4
No No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

StemmlerSisters and others added 2 commits March 16, 2024 13:20
@socket-security

Copy link
Copy Markdown

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
pypi/jinja2@3.1.3 environment, eval, filesystem, unsafe Transitive: shell +62 64.2 MB

🚮 Removed packages: pypi/jinja2@3.0.3, pypi/jinja2@3.0.3

View full report↗︎

pull Bot pushed a commit that referenced this pull request Jul 15, 2025
…2141)

I released a new version of contrib.glfw3 with a workaround/bug fix. I
wanted to point out that there is the same issue that was
[created](emscripten-core#18089) on
10/22 for the built-in implementation. That was never addressed. I also
wanted to point out that SDL2 also suffers from the same issue...

I found [this issue](ocornut/imgui#7732) while
working on a project using ImGui.


![Meta_V](https://github.com/ocornut/imgui/assets/357116/0cec5893-d146-40fe-ae15-2fd00e7bd319)

Release notes:
- Implemented workaround for
[#4](pongasoft/emscripten-glfw#4): _Using
Super + "Key" on macOS results in "Key" not being released_.
Due to the [broken
state](https://stackoverflow.com/questions/11818637/why-does-javascript-drop-keyup-events-when-the-metakey-is-pressed-on-mac-browser)
of javascript handling the `Super/Meta` key, there is no good solution.
The workaround implemented, releases all keys when `Super` is released.
Although not a perfect solution, it guarantees that the state is
_eventually_ consistent:
- if "Key" was released while "Super" was held, then when "Super" gets
released, "Key" is released (later than when actually released, final
state is consistent: "Key" in `Release` state)
- if "Key" is still held when "Super" is released, "Key" is released
when "Super" gets released, but immediately gets a down event (Up/Down
event, final state is consistent": "Key" in `Pressed` state)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants