[Snyk] Security upgrade python from 3.12-slim to 3.15-rc-alpine3.23

[kburger]

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):

• Dockerfile

We recommend upgrading to python:3.15-rc-alpine3.23, 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
	CVE-2005-2541 SNYK-DEBIAN13-TAR-5696683	187
	Out-of-Bounds SNYK-DEBIAN13-GLIBC-5681241	182
	Out-of-Bounds SNYK-DEBIAN13-GLIBC-5681241	182
	CVE-2019-1010023 SNYK-DEBIAN13-GLIBC-5681177	152
	CVE-2019-1010023 SNYK-DEBIAN13-GLIBC-5681177	152

---

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

[kburger]

@agjharms snyk suggests to move to an alpine release instead of the current slim image, upgrade from 3.12 to 3.15, and it uses an rc version. Is this something we can use, or do we prefer the same slim image, non rc, on a 3.12 branch? (assuming fixes to these vulnerabilities are available in a similar flavour)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud