[Snyk] Security upgrade python from 3.10-slim to 3.13.0rc2-slim

[fmigneault]

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

• docker/Dockerfile

We recommend upgrading to python:3.13.0rc2-slim, as this image has only 40 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
	Integer Overflow or Wraparound SNYK-DEBIAN12-EXPAT-7855502
	Integer Overflow or Wraparound SNYK-DEBIAN12-EXPAT-7855503
	XML External Entity (XXE) Injection SNYK-DEBIAN12-EXPAT-7855507
	Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963
	Uncontrolled Recursion SNYK-DEBIAN12-GCC12-2606941

---

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:

🦉 XML External Entity (XXE) Injection

[huard]

No objection, but we're not running this in prod yet. Has someone tested it to make sure there are not regression due to library versions?

[fmigneault]

Not tested. Snyk auto-PRs for Docker are always eager to pin RC versions, which I find very risky.
I'd limit the update to the latest 3.12 since this is the most recent that is officially listed in pyproject.toml and is tested by the CI.

[huard]

Agree, I suspect 3.13 would cause breakage.