Repository navigation
Update dependency certifi to v2026.10.19 [SECURITY] - autoclosed - #38
renovate[bot] wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update certifi pin requirements.txt |
The pinned certifi version changes to 2026.10.19. Both allowed hashes are replaced. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other
Possibly related issues
GortexAI/franco#5— The issue lists the certifi update to2026.10.19included in this change.
Possibly related PRs
- GortexAI/franco#37 — This PR changes the same certifi pin and replaces the package hashes.
Suggested reviewers: heminjoshi
Merge Risk: 
Minimal · up to f7046
-
The dependency update is correctly pinned and presents no identified merge-blocking risk.
Architecture risk: 
Low · up to f7046
-
The change affects 1 system.
Changed systems:
requirements.txtArchitecture concerns
No architecture-level concerns identified.Review details
-
Systems and components
- observed — requirements.txt (service) was modified; 1 changed file maps to changed impact.
Before / after behavior
- observed — Modified behavior in requirements.txt: The pinned
certifirelease changes from2026.7.22to2026.10.19, with both package hashes replaced.
-
Pre-merge checks: 
4 · 
1
-
Failed checks: 1 warning Passed checks: 4 passed-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Full details: Description check
-
Explanation
The description accurately explains the certifi update and its security purpose, but it does not follow the repository template. It omits the "What and why" heading, testing details, and the required checklist.
Resolution
Add the required template sections. State what changed and why, describe how the update was tested, and complete the checklist, including pytest results and confirmation that sending safety and repository data protections are unchanged or explain any changes.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
This PR contains the following updates:
2026.7.22→2026.10.19certifi 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 - G3root 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,urllib3andpip, 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:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
certifi/python-certifi (certifi)
v2026.10.19Compare Source
v2026.10.18Compare Source
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.
Summary by CodeRabbit