Skip to content

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

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
sihrc wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

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

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
Copy link

@cursor cursor bot Mar 5, 2026

Choose a reason for hiding this comment

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

Non-reproducible builds from unpinned latest base image

Medium Severity

Changing the base image from python:3.10.4 to python:latest makes the Docker build non-reproducible. When a new Python minor version (e.g., 3.14) is released, latest will automatically resolve to it, potentially breaking the build or runtime behavior without any code change. A pinned version like python:3.13 would fix the security vulnerabilities while preserving reproducibility. The uv sync --locked step is also more likely to fail if the resolved Python version drifts too far from what the lock file was generated against.

Fix in Cursor Fix in Web


ENV INDICO_HOST="try.indico.io"

Expand Down