Skip to content

[Snyk] Security upgrade nginx from 1.29.3-alpine to 1.29.5-alpine#150

Open
Dargon789 wants to merge 1 commit intomasterfrom
snyk-fix-5956ec35c654c165fbed453069411c2b
Open

[Snyk] Security upgrade nginx from 1.29.3-alpine to 1.29.5-alpine#150
Dargon789 wants to merge 1 commit intomasterfrom
snyk-fix-5956ec35c654c165fbed453069411c2b

Conversation

@Dargon789
Copy link
Owner

snyk-top-banner

Snyk has created this PR to fix 5 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):

  • docker/frontend/Dockerfile

We recommend upgrading to nginx:1.29.5-alpine, 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 Out-of-bounds Read
SNYK-ALPINE322-LIBPNG-15062355
  686  
high severity Out-of-bounds Read
SNYK-ALPINE322-LIBPNG-15062356
  686  
low severity CVE-2025-68160
SNYK-ALPINE322-OPENSSL-15121113
  436  
low severity CVE-2026-22796
SNYK-ALPINE322-OPENSSL-15121196
  436  
low severity CVE-2025-66199
SNYK-ALPINE322-OPENSSL-15121223
  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:

🦉 Out-of-bounds Read

@codesandbox
Copy link

codesandbox bot commented Feb 7, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link

snyk-io bot commented Feb 7, 2026

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

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist
Copy link

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, automatically generated by Snyk, focuses on enhancing the security posture of the application by updating the Nginx base image within the frontend Dockerfile. The primary goal is to address and mitigate several known vulnerabilities present in the older image, thereby ensuring a more secure and up-to-date deployment environment.

Highlights

  • Nginx Base Image Upgrade: The base Nginx image in docker/frontend/Dockerfile has been upgraded from nginx:1.29.3-alpine to nginx:1.29.5-alpine.
  • Vulnerability Resolution: This upgrade resolves 5 identified vulnerabilities, including two high-severity Out-of-bounds Read issues (SNYK-ALPINE322-LIBPNG-15062355, SNYK-ALPINE322-LIBPNG-15062356) and three low-severity OpenSSL CVEs (CVE-2025-68160, CVE-2026-22796, CVE-2025-66199).
Changelog
  • docker/frontend/Dockerfile
    • Updated the base image from nginx:1.29.3-alpine to nginx:1.29.5-alpine to incorporate security fixes.
Activity
  • This pull request was automatically created by Snyk to propose a security upgrade based on detected vulnerabilities.
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

@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 successfully upgrades the Nginx base image in the docker/frontend/Dockerfile from version 1.29.3-alpine to 1.29.5-alpine. This is a crucial update that addresses several identified security vulnerabilities, as detailed in the Snyk report. The change is straightforward and directly improves the security posture of the application's Docker image.

RUN npm run build

FROM nginx:1.29.3-alpine
FROM nginx:1.29.5-alpine

Choose a reason for hiding this comment

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

medium

To enhance reproducibility and prevent potential supply chain attacks, it is a best practice to pin Docker images to a specific digest rather than just a tag. While nginx:1.29.5-alpine is a good upgrade, consider adding the SHA256 digest to ensure that the exact same image is always used, even if the tag were to be repointed in the future. You can find the digest on Docker Hub or by pulling the image locally and inspecting it.

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