Skip to content

Conversation

@madisonmay
Copy link
Contributor

@madisonmay madisonmay commented Dec 16, 2025

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):

  • readme_docs/Dockerfile

We recommend upgrading to python:latest, as this image has only 189 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
high severity Out-of-bounds Write
SNYK-DEBIAN11-GLIBC-5927133
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN11-GLIBC-5927133
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN11-GLIBC-5927133
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN11-GLIBC-5927133
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN11-LIBWEBP-5893094
  829  

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:

🦉 Out-of-bounds Write


Note

Upgrade readme_docs/Dockerfile base image from python:3.9.15 to python:latest.

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

@@ -1,4 +1,4 @@
FROM python:3.9.15
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.

Bug: Using floating latest tag breaks build reproducibility

Changing from python:3.9.15 to python:latest creates non-reproducible builds since the latest tag is mutable and can change at any time. This conflicts with the uv sync --locked command on line 8, which is designed for reproducible installs. When latest points to a new Python version (e.g., beyond 3.13), the build may fail since dependencies like msgpack-numpy==0.4.4.3 may not support it yet. Consider using a specific version tag like python:3.12 or python:3.13 instead.

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.

3 participants