Skip to content

[Snyk] Security upgrade python from 3.10.4 to 3.14.3#433

Open
ashmuck wants to merge 1 commit intomasterfrom
snyk-fix-f86f548376f3aac06e4292b5cc61ff62
Open

[Snyk] Security upgrade python from 3.10.4 to 3.14.3#433
ashmuck wants to merge 1 commit intomasterfrom
snyk-fix-f86f548376f3aac06e4292b5cc61ff62

Conversation

@ashmuck
Copy link

@ashmuck ashmuck commented Feb 6, 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:3.14.3, as this image has only 219 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-LIBWEBP-5893094
  829  
high severity Out-of-bounds Write
SNYK-DEBIAN11-LIBWEBP-5893094
  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

Medium Risk
Base image upgrades can change Python/OS-level behavior and dependency compatibility, so the main risk is build/runtime regressions despite the diff being small.

Overview
Updates the Docker base image from python:3.10.4 to python:3.14.3 to pick up newer OS/Python security fixes in the build environment.

Written by Cursor Bugbot for commit 123e282. 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,4 +1,4 @@
FROM python:3.10.4
FROM python:3.14.3
Copy link

Choose a reason for hiding this comment

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

Major Python version jump skips untested versions

Medium Severity

The base image jumps from python:3.10.4 to python:3.14.3, skipping four minor versions. The project's pyproject.toml classifiers only declare support through Python 3.13, indicating 3.14 hasn't been validated. Key dependencies like jsons==1.6.3 (which depends on typish==1.9.3 from 2021) and msgpack-numpy==0.4.4.3 (from 2019) rely heavily on Python typing internals that frequently break across major versions. Runtime failures may not surface until the container starts.

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