Skip to content

[Snyk] Security upgrade python from 3.10.4 to latest #440

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nicholas-lockhart wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade python from 3.10.4 to latest #440

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM python:3.10.4
FROM python:latest

@cursor cursor Bot Mar 5, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Floating latest tag causes non-reproducible Docker builds

High Severity

Changing FROM python:3.10.4 to FROM python:latest makes the Docker build non-reproducible. The latest tag is a moving target — when a new Python version (e.g. 3.14) is released, it will be picked up automatically. This risks breaking uv sync --locked since the lockfile was resolved for specific Python version ranges, and pinned dependencies like msgpack-numpy==0.4.4.3 may lack wheels or compatibility with future Python versions. A specific version tag (e.g. python:3.13) would fix the security vulnerabilities while keeping builds deterministic.

Fix in Cursor Fix in Web


ENV INDICO_HOST="try.indico.io"

Expand Down