The Fix
pip install urllib3==1.26.20
Based on closed urllib3/urllib3 issue #3414 · PR/commit linked
@@ -220,6 +220,12 @@ Fixed
* Fixed ``urllib3.contrib.pyopenssl.WrappedSocket`` and ``urllib3.contrib.securetransport.WrappedSocket`` close methods (`#2970 <https://github.com/urllib3/urllib3/issues/2970>`__)
+1.26.19 (2024-06-17)
+====================
+
Option A — Upgrade to fixed release\npip install urllib3==1.26.20\nWhen NOT to use: This fix is not applicable if the changelog is already updated.\n\n
Why This Fix Works in Production
- Trigger: Change log for version 1.26.19
- Mechanism: Added changelog entry for version 1.26.19 to the main changelog.
- Why the fix works: Added changelog entry for version 1.26.19 to the main changelog. (first fixed release: 1.26.20).
Why This Breaks in Prod
- Production symptom (often without a traceback): Change log for version 1.26.19
Proof / Evidence
- GitHub issue: #3414
- Fix PR: https://github.com/urllib3/urllib3/pull/3415
- First fixed release: 1.26.20
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.95
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.64
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“please add the change log for version 1.26.19”
Failure Signature (Search String)
- Change log for version 1.26.19
- please add the change log for version `1.26.19`
Copy-friendly signature
Failure Signature
-----------------
Change log for version 1.26.19
please add the change log for version `1.26.19`
Error Message
Signature-only (no traceback captured)
Error Message
-------------
Change log for version 1.26.19
please add the change log for version `1.26.19`
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install urllib3==1.26.20
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/urllib3/urllib3/pull/3415
First fixed release: 1.26.20
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix is not applicable if the changelog is already updated.
Did This Fix Work in Your Case?
Quick signal helps us prioritize which fixes to verify and improve.
Prevention
- Add a CI check that diffs key outputs after upgrades (OpenAPI schema snapshots, JSON payload shapes, CLI output).
- Upgrade behind a canary and run integration tests against the canary before 100% rollout.
Version Compatibility Table
| Version | Status |
|---|---|
| 1.26.20 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.