[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.13-rc/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		Jan 31, 2026 8:28pm

[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 project's security by updating the Docker base image to a more recent and secure version of Alpine Linux. By upgrading from alpine:3.17 to alpine:3.23.3, the change effectively mitigates several known vulnerabilities, ensuring a more robust and protected application environment.

Highlights

• Security Upgrade: This pull request performs a security upgrade of the alpine base image used in the Dockerfile.
• Version Bump: The alpine base image is updated from version 3.17 to 3.23.3.
• Vulnerability Fixes: This upgrade addresses two high-severity vulnerabilities (CVE-2025-26519 in musl) and two low-severity vulnerabilities (CVE-2024-9143 in openssl).
• Automated PR: The pull request was automatically generated by Snyk to remediate identified security issues.

🧠 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, generated by Snyk, aims to fix security vulnerabilities by upgrading the Alpine base image from 3.17 to 3.23.3. While the intention is correct, the implementation is flawed. The change is made directly to a generated Dockerfile (3.13-rc/alpine3.17/Dockerfile), which will be overwritten. The correct approach is to update the versions.json file to specify the new Alpine version and then regenerate the Dockerfiles using the apply-templates.sh script. This will ensure the fix is permanent. Additionally, other Python versions in versions.json also use the vulnerable alpine:3.17 and should be updated as well.

[gemini-code-assist]

This change directly modifies a generated file, which is discouraged by the comment header in this file. The change will be overwritten the next time the apply-templates.sh script is run, making the fix ineffective.

To apply this security upgrade correctly and permanently, you should:

1. Update versions.json by changing the "alpine3.17" variant to "alpine3.23.3" for the 3.13-rc key.
2. Run the ./apply-templates.sh script. This will create a new 3.13-rc/alpine3.23.3/ directory with the updated Dockerfile.
3. Remove the old 3.13-rc/alpine3.17/ directory.

This change was likely made by an automated tool (Snyk) that isn't aware of the project's file generation process. Applying the fix as suggested will also resolve the inconsistency between the directory name (alpine3.17) and the base image version (3.23.3).