Skip to content

⬆️ chore(deps): update dependency certifi to v2026.10.18 [SECURITY] - #500

Merged
konih merged 1 commit into
mainfrom
renovate/pypi-certifi-vulnerability
Oct 30, 2026
Merged

konih merged 1 commit into
mainfrom
renovate/pypi-certifi-vulnerability

Conversation

@konih

@konih konih commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Change Age Confidence
certifi 2026.5.20 → 2026.10.18 age confidence

certifi bundles emSign root CAs with compromised intermediate CA keys

GHSA-6q48-6c7w-9gw2

More information

Details

Certifi versions before 2026.10.18 include the emSign ECC Root CA - G3 root certificate in their bundled CA store. Eight eMudhra intermediate CA certificates that chain to this root have compromised private keys and the CA has revoked them.

An attacker with one of the compromised keys can issue valid-looking certificates for any hostname. If the attacker is also on-path, they can intercept or modify TLS traffic from clients that trust the certifi bundle. Examples include requests, urllib3 and pip, and the Python.org macOS installer.

Certifi 2026.10.18 removed all emSign roots from the bundle. Certifi 2026.10.19 restored the emSign roots that are not affected. Upgrade to 2026.10.19 or later, and rebuild container images that vendor certifi.

Severity

  • CVSS Score: 9.1 / 10 (Critical)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

certifi/python-certifi (certifi)

v2026.10.18

Compare Source

v2026.7.22

Compare Source

v2026.6.17

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@konih konih added the dependencies Pull requests that update a dependency file label Oct 26, 2026
@konih
konih force-pushed the renovate/pypi-certifi-vulnerability branch from 5f8c979 to 6570456 Compare October 28, 2026 14:41
@konih konih changed the title ⬆️ chore(deps): update dependency certifi to v2026.10.19 [SECURITY] ⬆️ chore(deps): update dependency certifi to v2026.10.18 [SECURITY] Oct 28, 2026
@konih
konih force-pushed the renovate/pypi-certifi-vulnerability branch 4 times, most recently from 834ec19 to 72e8507 Compare October 29, 2026 23:23
@konih

konih commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator Author

Left open: dependency-review fails on licence policy, not on the bump itself. certifi 2026.10.18 is reported as MPL-2.0, which is not in the allow-licenses list in .github/workflows/ci.yaml. Merging needs an operator decision to allow certifi (a docs-build-only dependency) as a scoped allow-dependencies-licenses exception.

@konih
konih force-pushed the renovate/pypi-certifi-vulnerability branch from 72e8507 to f65b8b5 Compare October 30, 2026 06:00
konih added a commit that referenced this pull request Oct 30, 2026
Renovate #500 (certifi, MPL-2.0, docs build only), #512 (sonarqube-scan-action, LGPL-3.0, CI only) and #513 (golang.org/x/sys and x/tools, Go PATENTS ref like x/net) fail dependency-review. Scope each exception to its package, as for the existing ones.
@konih
konih force-pushed the renovate/pypi-certifi-vulnerability branch from f65b8b5 to 8abc9b9 Compare October 30, 2026 08:35
@konih
konih merged commit 2e3222d into main Oct 30, 2026
37 checks passed
@konih
konih deleted the renovate/pypi-certifi-vulnerability branch October 30, 2026 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants