Skip to content

[Snyk] Security upgrade python from 3.9-slim to 3.14.3-slim#126

Merged
Dargon789 merged 1 commit intomasterfrom
snyk-fix-e44315e3b983523832bb1b300abf6189
Feb 12, 2026
Merged

[Snyk] Security upgrade python from 3.9-slim to 3.14.3-slim#126
Dargon789 merged 1 commit intomasterfrom
snyk-fix-e44315e3b983523832bb1b300abf6189

Conversation

@Dargon789
Copy link
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 CVE-2025-69421
SNYK-DEBIAN13-OPENSSL-15123186
  686  
high severity CVE-2025-69421
SNYK-DEBIAN13-OPENSSL-15123186
  686  
high severity CVE-2025-69421
SNYK-DEBIAN13-OPENSSL-15123186
  686  
low severity CVE-2026-22795
SNYK-DEBIAN13-OPENSSL-15123206
  436  
low severity CVE-2025-11187
SNYK-DEBIAN13-OPENSSL-15123211
  436  

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.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the security posture of the application by upgrading its Docker base image. By moving to a more recent Python version, several known vulnerabilities are mitigated, ensuring a more secure and robust deployment environment.

Highlights

  • Python Base Image Upgrade: The Dockerfile has been updated to use python:3.14.3-slim instead of python:3.9-slim. This upgrade addresses 3 high-severity and 2 low-severity vulnerabilities, including CVE-2025-69421, CVE-2026-22795, and CVE-2025-11187.
Changelog
  • Dockerfile
    • Updated the base Python image from python:3.9-slim to python:3.14.3-slim.
Activity
  • This pull request was automatically generated by Snyk to address identified vulnerabilities in the project's Dockerfile dependencies.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link

github-actions bot commented Feb 9, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@vercel
Copy link

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
coinbase-ethereum-smartcontracts Ready Ready Preview, Comment Feb 12, 2026 7:35am
coinbase-smartcontracts Error Error Feb 12, 2026 7:35am

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, generated by Snyk, upgrades the Python base image in the Dockerfile from 3.9-slim to 3.14.3-slim to address security vulnerabilities. While the change itself is a straightforward version bump, I've identified a critical issue in the Dockerfile's structure. It incorrectly uses multi-stage builds, where the entire first stage for the Node.js application is built and then completely discarded. This makes the first 20 lines of the file ineffective, leading to an inefficient build process and potential confusion. My review comment details this issue and suggests how to resolve it.

@Dargon789 Dargon789 merged commit 0ffa229 into master Feb 12, 2026
10 of 13 checks passed
@Dargon789 Dargon789 deleted the snyk-fix-e44315e3b983523832bb1b300abf6189 branch February 12, 2026 10:55
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