Skip to content

[Snyk] Security upgrade python from 3.10.18-slim-trixie to 3.14.2-slim-trixie#65

Open
bybatkhuu wants to merge 1 commit intomainfrom
snyk-fix-4868adf520385bf7aef1556b3ea99a54
Open

[Snyk] Security upgrade python from 3.10.18-slim-trixie to 3.14.2-slim-trixie#65
bybatkhuu wants to merge 1 commit intomainfrom
snyk-fix-4868adf520385bf7aef1556b3ea99a54

Conversation

@bybatkhuu
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.2-slim-trixie, as this image has only 23 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
low severity CVE-2025-9231
SNYK-DEBIAN13-OPENSSL-13174592
  364  
low severity CVE-2025-9231
SNYK-DEBIAN13-OPENSSL-13174592
  364  
low severity CVE-2025-9230
SNYK-DEBIAN13-OPENSSL-13174602
  364  
low severity CVE-2025-9230
SNYK-DEBIAN13-OPENSSL-13174602
  364  
low severity CVE-2025-9232
SNYK-DEBIAN13-OPENSSL-13174605
  364  

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.
  • Snyk has automatically assigned this pull request, set who gets assigned.

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
👩‍💻 Set who automatically gets assigned
📜 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.

Copilot AI review requested due to automatic review settings December 15, 2025 09:57
@bybatkhuu bybatkhuu self-assigned this Dec 15, 2025
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR upgrades the Python Docker base image from 3.10.18-slim-trixie to 3.14.2-slim-trixie to address OpenSSL security vulnerabilities (CVE-2025-9230, CVE-2025-9231, CVE-2025-9232) as identified by Snyk security scanning.

Key Changes:

  • Updates the BASE_IMAGE argument from Python 3.10.18 to 3.14.2
  • Maintains the same slim-trixie Debian base and configuration
  • Addresses 3 low-severity OpenSSL CVEs through the base image update

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Dockerfile
# syntax=docker/dockerfile:1

ARG BASE_IMAGE=python:3.10.18-slim-trixie
ARG BASE_IMAGE=python:3.14.2-slim-trixie
Copy link

Copilot AI Dec 15, 2025

Choose a reason for hiding this comment

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

This is a major version jump from Python 3.10 to 3.14, which skips three minor versions (3.11, 3.12, 3.13). Each of these versions introduced breaking changes and deprecations. While the Dockerfile uses certbot and certbot-dns-cloudflare which are generally compatible, this large version jump increases the risk of compatibility issues. Additionally, the GitHub workflow (.github/workflows/publish-docs.yml) and pre-commit configuration (.pre-commit-config.yaml) still reference Python 3.10, which will create inconsistency between development and production environments. Consider updating those files to match, or testing with Python 3.13 first as a more conservative intermediate step.

Suggested change
ARG BASE_IMAGE=python:3.14.2-slim-trixie
ARG BASE_IMAGE=python:3.13-slim

Copilot uses AI. Check for mistakes.
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