[Snyk] Security upgrade python from 3.14.0rc2-alpine3.22 to 3.14.0-alpine3.22

[hashim21223445]

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.0-alpine3.22, as this image has only 0 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
	CVE-2025-9232 SNYK-ALPINE322-OPENSSL-13174131	54
	CVE-2025-9232 SNYK-ALPINE322-OPENSSL-13174131	54
	CVE-2025-9230 SNYK-ALPINE322-OPENSSL-13174132	54
	CVE-2025-9230 SNYK-ALPINE322-OPENSSL-13174132	54
	CVE-2025-9231 SNYK-ALPINE322-OPENSSL-13174133	54

---

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.

[semanticdiff-com]

Review changes with  

[gemini-code-assist]

Summary of Changes

Hello @hashim21223445, I'm Gemini Code Assist¹! 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, automatically generated by Snyk, focuses on enhancing the security posture of the project by updating the Docker base image. It transitions the Python environment from a release candidate version to its stable release, specifically upgrading from python:3.14.0rc2-alpine3.22 to python:3.14.0-alpine3.22, which effectively mitigates multiple identified low-severity OpenSSL vulnerabilities.

Highlights

• Security Upgrade: Upgraded the Python base image in the Dockerfile from 3.14.0rc2-alpine3.22 to 3.14.0-alpine3.22 to enhance security.
• Vulnerability Fixes: This upgrade addresses 3 low-severity vulnerabilities (CVE-2025-9232, CVE-2025-9230, CVE-2025-9231) related to OpenSSL within the Docker image 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. ↩

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[Copilot]

Pull Request Overview

This PR upgrades the Python Docker base image from a release candidate version to the stable release to address security vulnerabilities. Snyk has identified 3 OpenSSL-related vulnerabilities in the current base image that will be fixed with this upgrade.

Key changes:

• Upgrade Python Docker base image from 3.14.0rc2-alpine3.22 to 3.14.0-alpine3.22
• Addresses 5 instances of 3 distinct CVEs (CVE-2025-9232, CVE-2025-9230, CVE-2025-9231) in OpenSSL components

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[gemini-code-assist]

Code Review

This pull request from Snyk upgrades the Python base image from a release candidate (3.14.0rc2-alpine3.22) to a stable version (3.14.0-alpine3.22), which is a positive change for security and stability. My review includes a suggestion to further enhance the Dockerfile's robustness by pinning the base image to its immutable SHA256 digest. Additionally, while reviewing the file, I noticed an unrelated issue in the Dockerfile: the command COPY setup.py /igel/setup.py is duplicated on lines 13 and 15. Removing the redundant line would be a good cleanup.

[gemini-code-assist]

For improved security and build reproducibility, it's a best practice to pin the base image to its immutable digest (SHA256) instead of a mutable tag. This protects against tag mutability, where the python:3.14.0-alpine3.22 tag could be updated to point to a different image digest.

You can find the digest for the image (for example, by running docker pull python:3.14.0-alpine3.22 and then docker inspect python:3.14.0-alpine3.22) and update the FROM instruction like this:

FROM python:3.14.0-alpine3.22@sha256:<the-sha256-digest-of-the-image>

This ensures that you are always using the exact same base image for your builds.