CVE-2026-27448: pyOpenSSL allows TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback

Published Mar 16, 2026
·
Updated

If a user provided callback to settlsextservernamecallback 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.

Other sources

pyOpenSSL allows TLS connection bypass via unhandled callback exception in settlsextservernamecallback

Microsoft

pyOpenSSL is a Python wrapper around the OpenSSL library. Starting in version 0.14.0 and prior to version 26.0.0, if a user provided callback to settlsextservernamecallback 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. Starting in version 26.0.0, unhandled exceptions now result in rejecting the connection.

MITRE

Affected Software

4 affected componentsFixes available
pip/pyopenssl>=0.14.0<26.0.0
26.0.0
Microsoft azl3 pyOpenSSL 24.2.1-1
pyopenssl pyopenssl>=0.14<26.0.0
debian/pyopenssl<=20.0.1-1, <=23.0.0-1, <=25.0.0-1
26.1.0-1

Event History

Mar 16, 2026
Advisory Published
via GitHub·03:15 PM
Data Sourced
via GitHub·03:15 PM
DescriptionWeaknessAffected Software
Mar 17, 2026
CVE Published
via MITRE·11:24 PM
Data Sourced
via MITRE·11:24 PM
DescriptionWeakness
Mar 18, 2026
Data Sourced
via NVD·12:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 19, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
May 28, 2026
Data Sourced
via Ubuntu·03:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·03:16 PM
DescriptionAffected Software
Data Sourced
via Launchpad·03:16 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-27448?

CVE-2026-27448 has a medium severity level due to the potential for bypassing security-sensitive behaviors.

2

How do I fix CVE-2026-27448?

To fix CVE-2026-27448, update pyopenssl to version 26.0.0 or later.

3

What happens if the callback provided to set_tlsext_servername_callback raises an exception in CVE-2026-27448?

If the callback raises an unhandled exception, the connection will be accepted, potentially allowing security bypass.

4

Who is affected by CVE-2026-27448?

Users of pyopenssl versions between 0.14.0 and 26.0.0 are affected by CVE-2026-27448.

5

What is the impact of CVE-2026-27448 on applications using pyopenssl?

Applications relying on the set_tlsext_servername_callback for security-sensitive behavior may be at risk of connection acceptance despite exceptions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203