pyopenssl vulnerabilities
Python wrapper module around the OpenSSL library
- Registry
- PyPI
- Latest
- 26.4.0
- License
- Apache License, Version 2.0
5 known advisories
The latest version, 26.4.0, is not affected by any of them. Projects on older versions may be.
pip install 'pyopenssl>=26.4.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
Security advisories for pyopenssl
pyOpenSSL DTLS cookie callback buffer overflow
- Affected
- >=22.0.0 <26.0.0
- Fixed in
- 26.0.0
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
PyOpenSSL Mishandles NUL Byte In Certificate Subject Alternative Name
- Affected
- <0.13.1
- Fixed in
- 0.13.1
PyOpenSSL Use-After-Free vulnerability
- Affected
- <17.5.0
- Fixed in
- 17.5.0
Pyopenssl Incorrect Memory Management
- Affected
- <17.5.0
- Fixed in
- 17.5.0
Is your pyopenssl version vulnerable?
- pyopenssl 26.4No known advisories in 26.4.0
- pyopenssl 26.3No known advisories in 26.3.0
- pyopenssl 26.2No known advisories in 26.2.0
- pyopenssl 26.1No known advisories in 26.1.0
- pyopenssl 26.0No known advisories in 26.0.0
- pyopenssl 25.32 advisories in 25.3.0
- pyopenssl 25.22 advisories in 25.2.0
- pyopenssl 25.12 advisories in 25.1.0
- pyopenssl 25.02 advisories in 25.0.0
- pyopenssl 24.32 advisories in 24.3.0
- pyopenssl 24.22 advisories in 24.2.1
- pyopenssl 24.12 advisories in 24.1.0
- pyopenssl 24.02 advisories in 24.0.0
Which of your client projects still run an old pyopenssl?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.