LowGHSA-vp96-hxj8-p424CVE-2026-27448PYSEC-2026-2268

pyOpenSSL allows TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback

Published 16 Mar 2026 · Updated 10 Sept 2026

Is your project on an affected pyopenssl?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=0.14.0 <26.0.0
Fixed in
26.0.0
Update to the fixed version for your release line, for example:pip install 'pyopenssl>=26.0.0'

Details

If a user provided callback to set_tlsext_servername_callback raised an unhandled exception, this would result in a connection being accepted. If a user was relying on this callback for any security-sensitive behavior, this could allow bypassing it.

Unhandled exceptions now result in rejecting the connection.

Credit to Leury Castillo for reporting this issue.

Is GHSA-vp96-hxj8-p424 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pyopenssl, and gives you the command that fixes it.

More advisories for pyopenssl

  • HighCVE-2026-27459pyOpenSSL DTLS cookie callback buffer overflow · 16 Mar 2026
  • HighCVE-2013-4314PyOpenSSL Mishandles NUL Byte In Certificate Subject Alternative Name · 17 May 2022
  • HighCVE-2018-1000807PyOpenSSL Use-After-Free vulnerability · 10 Oct 2018
  • HighCVE-2018-1000808Pyopenssl Incorrect Memory Management · 10 Oct 2018
pyopenssl security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.