Skip to content

Require certifi>=2026.10.19 and pip>=26.2.2 (GHSA-6q48-6c7w-9gw2) - #1565

Closed
kaggle-marvin wants to merge 1 commit into
Kaggle:mainfrom
kaggle-marvin:certifi-ghsa-6q48
Closed

kaggle-marvin wants to merge 1 commit into
Kaggle:mainfrom
kaggle-marvin:certifi-ghsa-6q48

Conversation

@kaggle-marvin

Copy link
Copy Markdown

certifi before 2026.10.19 trusts the emSign ECC Root CA - G3, whose intermediate CAs have compromised private keys (GHSA-6q48-6c7w-9gw2). Python TLS clients don't check revocation, so anything using the old bundle accepts certificates minted with those keys, for any host.

The notebook image doesn't pin certifi; it inherits whatever the Colab base image ships. This adds floors to kaggle_requirements.txt, so the next build is guaranteed to be patched:

  • certifi>=2026.10.19
  • pip>=26.2.2: older pip always loads its own vendored certifi, even when the system one is fixed (python.org notice).

tests/test_certifi.py checks the versions and that the emSign ECC G3 root is gone from the bundle.

Not covered here: the gcloud SDK's bundled certifi (b/575852372).

Bug: http://b/575927270

@kaggle-marvin

Copy link
Copy Markdown
Author

Closing at the maintainer's request; the fix will land through a PR from a Kaggle/docker-python branch instead.

@kaggle-marvin
kaggle-marvin deleted the certifi-ghsa-6q48 branch October 20, 2026 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants