Skip to content

[Snyk] Security upgrade alpine from 3.17 to 3.23.3#27

Open
tpsaint wants to merge 1 commit intomasterfrom
snyk-fix-c7bc6293c166e69542791d90566db8b3
Open

[Snyk] Security upgrade alpine from 3.17 to 3.23.3#27
tpsaint wants to merge 1 commit intomasterfrom
snyk-fix-c7bc6293c166e69542791d90566db8b3

Conversation

@tpsaint
Copy link
Copy Markdown
Owner

@tpsaint tpsaint commented Feb 2, 2026

snyk-top-banner

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.8/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
high severity CVE-2025-26519
SNYK-ALPINE317-MUSL-8720633
  614  
high severity CVE-2025-26519
SNYK-ALPINE317-MUSL-8720633
  614  
low severity CVE-2024-9143
SNYK-ALPINE317-OPENSSL-8235199
  364  
low severity 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
Copy link
Copy Markdown

vercel bot commented Feb 2, 2026

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

Project Deployment Actions Updated (UTC)
python Error Error Feb 2, 2026 10:00pm

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @tpsaint, 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 automates a critical security update by upgrading the base Alpine Linux image used in a Dockerfile. The primary goal is to mitigate known vulnerabilities present in the older image version, thereby enhancing the security posture of the containerized application.

Highlights

  • Alpine Base Image Upgrade: The alpine base image in 3.8/alpine3.17/Dockerfile has been upgraded from version 3.17 to 3.23.3.
  • Security Vulnerability Fixes: This upgrade addresses multiple high and low severity vulnerabilities, including CVE-2025-26519 and CVE-2024-9143, found in the alpine:3.17 image, aiming to improve the project's security posture.

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

Copy link
Copy Markdown

@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, automatically generated by Snyk, attempts to upgrade the Alpine base image to fix security vulnerabilities. However, it modifies a generated file directly, which is explicitly discouraged by comments in the file. The correct approach is to update the template generation scripts (versions.sh, apply-templates.sh) to ensure the change is applied consistently across all Dockerfiles and is not overwritten. The current change is incorrect as it only patches one of several vulnerable files and will be lost when the generation scripts are run again.

#

FROM alpine:3.17
FROM alpine:3.23.3
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This change directly modifies a generated file, which is warned against in the file's header. This change will be overwritten the next time the apply-templates.sh script is run.

The correct way to update the base image is to modify the generation source. Specifically:

  1. Update the hardcoded Alpine versions in versions.sh.
  2. Execute versions.sh to update versions.json.
  3. Execute apply-templates.sh to regenerate all Dockerfiles for all Python versions.

This approach ensures that:

  • The change is permanent and not overwritten.
  • The vulnerability is fixed in all Dockerfiles using alpine:3.17 (for Python versions 3.8, 3.9, 3.10, 3.11, 3.12, and 3.13-rc), not just this one.
  • The directory name will be updated to match the new Alpine version (e.g., .../alpine3.23/), avoiding confusion.

Because this PR takes an incorrect approach and only provides a partial fix, it should be closed and the fix should be re-implemented correctly.

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