Is pyopenssl 20.0 vulnerable?
PyPI · 2 releases from 20.0.0 to 20.0.1 · latest pyopenssl is 26.4.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. pyopenssl 20.0.1, the last 20.0 release, is affected by 1 known security advisory (1 low), including CVE-2026-27448. Upgrade to 26.0.0 or later to fix all of them.
pip install 'pyopenssl>=26.0.0'Is your project on an affected pyopenssl?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting pyopenssl 20.0.1
pyOpenSSL allows TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback
- Affected
- >=0.14.0 <26.0.0
- Fixed in
- 26.0.0
Every pyopenssl 20.0.x release
Affected: 20.0.0 to 20.0.1. Latest pyopenssl: 26.4.0.
| Version | Known advisories |
|---|---|
| pyopenssl 20.0.1 | CVE-2026-27448 |
| pyopenssl 20.0.0 | CVE-2026-27448 |
Which of your client projects are still on pyopenssl 20.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact pyopenssl version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other pyopenssl versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.