[Snyk] Security upgrade nginx from alpine to 1.25.3-alpine3.18

[molllyn1]

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

• config/docker/Dockerfile

We recommend upgrading to nginx:1.25.3-alpine3.18, 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
	514	Out-of-bounds Read SNYK-ALPINE318-LIBX11-6042396	No Known Exploit
	514	Loop with Unreachable Exit Condition ('Infinite Loop') SNYK-ALPINE318-LIBX11-6042397	No Known Exploit
	614	Integer Overflow or Wraparound SNYK-ALPINE318-LIBX11-6042398	No Known Exploit
	586	Improper Check for Unusual or Exceptional Conditions SNYK-ALPINE318-OPENSSL-6055795	No Known Exploit
	586	Improper Check for Unusual or Exceptional Conditions SNYK-ALPINE318-OPENSSL-6055795	No Known Exploit

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[guardrails]

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

Mode: paranoid | Total findings: 1 | Considered vulnerability: 1

Insecure Access Control (1)

Severity	Details	Docs
High	Title: Missing User Instruction redoc/config/docker/Dockerfile Line 25 in fa9a4d0 FROM nginx:1.25.3-alpine3.18	📚

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

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.