[Snyk] Security upgrade alpine from 3.17 to 3.23.3

[tpsaint]

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):

• 3.11/alpine3.17/Dockerfile

We recommend upgrading to alpine:3.23.3, 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-26519 SNYK-ALPINE317-MUSL-8720633	614
	CVE-2025-26519 SNYK-ALPINE317-MUSL-8720633	614
	CVE-2024-9143 SNYK-ALPINE317-OPENSSL-8235199	364
	CVE-2024-9143 SNYK-ALPINE317-OPENSSL-8235199	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.

---

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.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
python	Error		Feb 1, 2026 11:21pm

[gemini-code-assist]

Summary of Changes

Hello @tpsaint, 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 significantly improves the security of the project by updating the Docker base image to a more recent and secure version. The primary goal is to eliminate known vulnerabilities present in the older Alpine Linux version, ensuring the application runs on a hardened and patched environment.

Highlights

• Base Image Upgrade: The Docker base image has been upgraded from alpine:3.17 to alpine:3.23.3.
• Security Vulnerability Fixes: This upgrade addresses 2 high-severity and 2 low-severity vulnerabilities, including CVE-2025-26519 and CVE-2024-9143, resulting in a base image with 0 known vulnerabilities.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to enhance security by upgrading the Alpine base image from version 3.17 to 3.23.3. While the intention is correct, the current implementation modifies a file that is auto-generated. This means the changes will be lost when the generation script is run, rendering the security fix temporary. Furthermore, the fix is incomplete as it only addresses one of several Dockerfiles built from the vulnerable base image. My review includes a critical comment on the Dockerfile change, explaining these issues and suggesting the correct way to apply this update by modifying the project's configuration files.

[gemini-code-assist]

This change correctly identifies and updates the vulnerable Alpine base image. However, there are two major issues with this approach:

1. Modification of a generated file: As noted in the file's header, this Dockerfile is generated by apply-templates.sh. Direct edits will be overwritten when the script is run again, undoing the security fix. The correct approach is to modify the source configuration file, versions.json.

2. Incomplete fix: The alpine:3.17 base image is used for multiple Python versions (3.8, 3.9, 3.10, 3.11, 3.12, and 3.13-rc) according to versions.json. This PR only fixes the issue for Python 3.11. The vulnerability will persist in the Docker images for other Python versions.

To properly resolve this, versions.json should be updated to replace all occurrences of alpine3.17 with a new variant name (e.g., alpine3.23.3 to match the version in this PR), and then the apply-templates.sh script should be run to regenerate all affected Dockerfiles. This will ensure the fix is permanent and comprehensive across all supported Python versions.