[Snyk] Security upgrade nginx from 1.21 to 1.26.0

[Rubix982]

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-server/Dockerfile

We recommend upgrading to nginx:1.26.0, as this image has only 103 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
	714	Double Free SNYK-DEBIAN11-CURL-1585150	No Known Exploit
	829	Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133	Mature
	829	Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133	Mature
	829	Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094	Mature
	844	Resource Exhaustion SNYK-DEBIAN11-NGHTTP2-5953384	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
🦉 Double Free

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[guardrails]

⚠️ We detected 1 security issue in this pull request:

Insecure Access Control (1)

Severity	Details	Docs
High	Title: Missing User Instruction ASP.NET-ReactJS-Template/web-server/Dockerfile Line 1 in fbaf97f FROM nginx:1.26.0	📚

More info on how to fix Insecure Access Control in Dockerfile.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.