[Snyk] Security upgrade python from 3.8-slim to 3.14.3-slim

[seigpe]

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

• build_tools/docker/py38.dockerfile

We recommend upgrading to python:3.14.3-slim, as this image has only 26 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-2025-6965 SNYK-DEBIAN12-SQLITE3-10753055	714
	CVE-2025-69421 SNYK-DEBIAN12-OPENSSL-15123192	686
	CVE-2025-69421 SNYK-DEBIAN12-OPENSSL-15123192	686
	Resource Exhaustion SNYK-DEBIAN12-EXPAT-6227597	614
	Directory Traversal SNYK-DEBIAN12-PAM-10378969	614

---

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:

🦉 Resource Exhaustion
🦉 Directory Traversal

[deepsource-io]

DeepSource Code Review

DeepSource reviewed changes in the commit range 6b0eb52..101eb82 on this pull request. Below is the summary for the review, and you can see the individual issues we found as review comments.

For detailed review results, please see the PR on DeepSource ↗

PR Report Card

Security	× 0 issues		Overall PR Quality
Reliability	× 0 issues
Complexity	× 0 issues
Hygiene	× 0 issues

Code Review Summary

Analyzer	Status	Summary	Details
Python		No new issues detected.	Review ↗
Shell		No new issues detected.	Review ↗

How are these analyzer statuses calculated?

Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings.