Skip to content

[Snyk] Security upgrade python from 3.9 to latest#5

Open
ashmuck wants to merge 1 commit intomasterfrom
snyk-fix-43d8a8843820d87d73214013c505297b
Open

[Snyk] Security upgrade python from 3.9 to latest#5
ashmuck wants to merge 1 commit intomasterfrom
snyk-fix-43d8a8843820d87d73214013c505297b

Conversation

@ashmuck
Copy link

@ashmuck ashmuck commented Mar 5, 2026

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • Dockerfile

We recommend upgrading to python:latest, as this image has only 260 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Heap-based Buffer Overflow
SNYK-DEBIAN13-IMAGEMAGICK-15044354
  714  
critical severity Heap-based Buffer Overflow
SNYK-DEBIAN13-IMAGEMAGICK-15044354
  714  
critical severity Release of Invalid Pointer or Reference
SNYK-DEBIAN13-IMAGEMAGICK-15044366
  714  
critical severity Release of Invalid Pointer or Reference
SNYK-DEBIAN13-IMAGEMAGICK-15044366
  714  
critical severity Release of Invalid Pointer or Reference
SNYK-DEBIAN13-IMAGEMAGICK-15044366
  714  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Heap-based Buffer Overflow


Note

Medium Risk
Using python:latest introduces a moving runtime target that can change behavior across builds and potentially break CI unexpectedly, despite being a small diff.

Overview
Updates the GitHub Actions-only Dockerfile base image from python:3.9 to python:latest to pick up newer security fixes in the underlying image.

Written by Cursor Bugbot for commit 3b35c85. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

@@ -1,5 +1,5 @@
# This Dockerfile is only for GitHub Actions
FROM python:3.9
FROM python:latest
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unpinned latest tag breaks build with incompatible Python

High Severity

Changing from python:3.9 to python:latest (currently Python 3.14) will almost certainly break the pip install . step on line 15. The project's setup.py only classifies support for Python 3.6–3.9, and its dependencies have tight upper bounds incompatible with Python 3.12+: invoke>=1.4.1,<2 has known issues on 3.12+, tomlkit>=0.10.0,<0.11.0 lacks 3.12+ support, and Python 3.12 removed distutils/imp which old dependency versions rely on. Additionally, latest is a moving target, making builds non-reproducible.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants