Skip to content

[Snyk] Security upgrade nginx from 1.29.2-alpine to 1.29.5-alpine#211

Open
Dargon789 wants to merge 2 commits intomasterfrom
snyk-fix-75e07a3b5d5ca979e0786880d1fa7083
Open

[Snyk] Security upgrade nginx from 1.29.2-alpine to 1.29.5-alpine#211
Dargon789 wants to merge 2 commits intomasterfrom
snyk-fix-75e07a3b5d5ca979e0786880d1fa7083

Conversation

@Dargon789
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 4 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-examples/v5/reverse_proxy/nginx_relative/nginx/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
critical severity Out-of-bounds Write
SNYK-ALPINE322-PCRE2-13637025
  232  
high severity Out-of-bounds Read
SNYK-ALPINE322-LIBPNG-15062355
  170  
high severity CVE-2025-69421
SNYK-ALPINE322-OPENSSL-15121226
  161  
high severity CVE-2025-69421
SNYK-ALPINE322-OPENSSL-15121226
  161  
high severity Out-of-bounds Read
SNYK-ALPINE322-LIBPNG-15062356
  115  

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 Write
🦉 Out-of-bounds Read

@gemini-code-assist
Copy link
Copy Markdown

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, aims to enhance the security posture of the project by updating the Nginx Docker base image. The upgrade addresses several critical and high-severity vulnerabilities present in the older image, ensuring a more secure deployment environment.

Highlights

  • Security Upgrade: Automatically upgraded the 'nginx' Docker base image from '1.29.2-alpine' to '1.29.5-alpine' to address multiple security vulnerabilities.
  • Vulnerability Fixes: This upgrade resolves 4 identified vulnerabilities, including critical and high-severity issues such as Out-of-bounds Write (PCRE2), Out-of-bounds Read (libpng), and CVE-2025-69421 (OpenSSL).
Changelog
  • docker-examples/v5/reverse_proxy/nginx_relative/nginx/Dockerfile
    • Upgraded the Nginx base image version.
Activity
  • This pull request was automatically created by Snyk to propose a security upgrade.
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
Copy link
Copy Markdown

snyk-io Bot commented Feb 10, 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.

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 upgrades the nginx base image from 1.29.2-alpine to 1.29.5-alpine to fix several security vulnerabilities. This upgrade specifically addresses known vulnerabilities in packages like pcre2, libpng, and openssl (e.g., CVE-2025-69421). A security review confirmed that no new vulnerabilities were introduced by these changes. To further enhance security and build reproducibility, consider pinning the Docker image to its immutable SHA256 digest.

@@ -1,2 +1,2 @@
FROM nginx:1.29.2-alpine
FROM nginx:1.29.5-alpine
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

For enhanced security and deterministic builds, it's a best practice to pin Docker images to their immutable digest (SHA256 hash). While using a specific version tag like 1.29.5-alpine is good, tags are mutable and can be updated. Pinning to the digest ensures you are always using the exact same image.

You can find the digest after pulling the image (docker pull nginx:1.29.5-alpine) and then inspecting it. The FROM instruction should be updated to include the digest:

FROM nginx:1.29.5-alpine@sha256:<image-digest-goes-here>

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