[Snyk] Security upgrade python from 3.9-slim to 3.13.2-slim

[gitafolabi]

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

• voting-app/vote/Dockerfile

We recommend upgrading to python:3.13.2-slim, as this image has only 38 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
	Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963	500
	CVE-2025-24528 SNYK-DEBIAN12-KRB5-8679228	221
	CVE-2025-24528 SNYK-DEBIAN12-KRB5-8679228	221
	CVE-2024-13176 SNYK-DEBIAN12-OPENSSL-8648323	150
	CVE-2024-13176 SNYK-DEBIAN12-OPENSSL-8648323	150

---

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:

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

[dryrunsecurity]

DryRun Security Summary

A Python voting app's Dockerfile upgrade from 3.9 to 3.13.2 slim revealed multiple security vulnerabilities, including unencrypted HTTP traffic, root-level container execution, unconstrained pip installations, insecure logging practices, and lack of runtime security hardening.

Expand for full summary

Python voting app Dockerfile updated from Python 3.9 to 3.13.2 slim image with multiple security considerations identified. Security vulnerabilities include:

1. Exposing port 80 (HTTP) without TLS/SSL protection
2. Running container as root with no user permission restrictions
3. Using pip install without version constraints, potentially introducing dependencies with unknown vulnerabilities
4. Logging directly to stdout/stderr with potential sensitive information exposure
5. No runtime security hardening implemented in the container configuration

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

View PR in the DryRun Dashboard.