Skip to content

[Snyk] Security upgrade python from 3.11.0b3-slim to 3.14.3-slim#155

Open
SPH73 wants to merge 1 commit into
mainfrom
snyk-fix-7d4e28751c2dc14037f577eac70baa76
Open

[Snyk] Security upgrade python from 3.11.0b3-slim to 3.14.3-slim#155
SPH73 wants to merge 1 commit into
mainfrom
snyk-fix-7d4e28751c2dc14037f577eac70baa76

Conversation

@SPH73

@SPH73 SPH73 commented Feb 8, 2026

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 3 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-slim, as this image has only 26 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 Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN11-SYSTEMD-6277510
  721  
high severity Allocation of Resources Without Limits or Throttling
SNYK-DEBIAN11-SYSTEMD-6277510
  721  
critical severity CVE-2024-37371
SNYK-DEBIAN11-KRB5-7411316
  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:

🦉 Out-of-bounds Write
🦉 Allocation of Resources Without Limits or Throttling


Note

Medium Risk
Python runtime and underlying Debian package versions change, which can introduce dependency/runtime incompatibilities despite the diff being small.

Overview
Updates the Docker base image from python:3.11.0b3-slim to python:3.14.3-slim to pick up upstream security fixes and reduce known OS/package vulnerabilities.

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

@cursor cursor Bot left a comment

Copy link
Copy Markdown

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.

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on March 31

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Comment thread Dockerfile
@@ -1,5 +1,5 @@
# Pull base image
FROM python:3.11.0b3-slim
FROM python:3.14.3-slim

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Python version incompatibility with project dependencies

High Severity

Upgrading to python:3.14.3-slim creates a major compatibility issue with the project's dependencies. The Pipfile explicitly requires python_version = "3.8", and the locked dependencies (Django 3.1.4, psycopg2-binary 2.8.6, etc.) are from 2020-2021 and do not support Python 3.14. Django 3.1 only supports Python 3.6 through 3.9. The pipenv install --system command will likely fail or produce a broken environment, and the application will not run correctly on Python 3.14.

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