Skip to content

[Snyk] Security upgrade nginx from 1.23.1-alpine to 1.26-alpine#147

Open
ThorntonMatthewD wants to merge 1 commit into
masterfrom
snyk-fix-d741f49b9b4fa49b528838a76c3a2a66
Open

[Snyk] Security upgrade nginx from 1.23.1-alpine to 1.26-alpine#147
ThorntonMatthewD wants to merge 1 commit into
masterfrom
snyk-fix-d741f49b9b4fa49b528838a76c3a2a66

Conversation

@ThorntonMatthewD

Copy link
Copy Markdown
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Changes included in this PR

  • web/Dockerfile

We recommend upgrading to nginx:1.26-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity Priority Score / 1000 Issue Exploit Maturity
critical severity 714 Cleartext Transmission of Sensitive Information
SNYK-ALPINE316-CURL-3320719
No Known Exploit
critical severity 714 Out-of-bounds Write
SNYK-ALPINE316-CURL-5958908
No Known Exploit
critical severity 714 Out-of-bounds Write
SNYK-ALPINE316-CURL-5958908
No Known Exploit
high severity 829 Out-of-bounds Write
SNYK-ALPINE316-LIBWEBP-5902237
Mature
high severity 829 Resource Exhaustion
SNYK-ALPINE316-NGHTTP2-6043732
Mature

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

🛠 Adjust project settings


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Resource Exhaustion

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