Skip to content

Conversation

@AkobArm
Copy link
Owner

@AkobArm AkobArm commented Dec 21, 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):

  • Dockerfile

We recommend upgrading to python:3.13.11, 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 CVE-2025-27363
SNYK-DEBIAN12-FREETYPE-9402511
  829  
high severity CVE-2025-27363
SNYK-DEBIAN12-FREETYPE-9402511
  829  
high severity CVE-2025-27363
SNYK-DEBIAN12-FREETYPE-9402511
  829  
critical severity Link Following
SNYK-DEBIAN12-GIT-6846203
  821  
critical severity Link Following
SNYK-DEBIAN12-GIT-6846203
  821  

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


Note

Upgrade Dockerfile Python base image from 3.12.1 to 3.13.11 in both build and runtime stages.

  • Docker:
    • Upgrade base image in Dockerfile from python:3.12.1 to python:3.13.11 for both the requirements and runtime stages.

Written by Cursor Bugbot for commit 741739a. 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.

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

Your free Bugbot reviews will reset on January 27

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.

RUN poetry export -f requirements.txt --output requirements.txt --without-hashes

FROM python:3.12.1
FROM python:3.13.11
Copy link

Choose a reason for hiding this comment

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

asyncpg 0.29.0 incompatible with Python 3.13 upgrade

Upgrading from Python 3.12 to 3.13 breaks the build because asyncpg version 0.29.0 in poetry.lock lacks Python 3.13 wheel support and fails to compile from source due to deprecated C API usage (Py_TRASHCAN_SAFE_BEGIN). Python 3.13 support was added in asyncpg 0.30. The poetry.lock file needs updating to a compatible asyncpg version before this Python upgrade can work.

Additional Locations (1)

Fix in Cursor Fix in Web

RUN poetry export -f requirements.txt --output requirements.txt --without-hashes

FROM python:3.12.1
FROM python:3.13.11
Copy link

Choose a reason for hiding this comment

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

greenlet 3.0.3 incompatible with Python 3.13 upgrade

The greenlet package version 3.0.3 locked in poetry.lock lacks Python 3.13 wheel support and fails to compile from source on Python 3.13. This package is required by SQLAlchemy's asyncio extras (used in pyproject.toml). Python 3.13 support was added in greenlet 3.1.0. The build will fail even if asyncpg is updated, requiring poetry.lock updates for both dependencies.

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