CVE-2026-27448

CVE-2026-27448 is a low-severity security vulnerability in pyopenssl (pip), affecting versions >= 0.14.0, < 26.0.0. It is fixed in 26.0.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

pyOpenSSL allows TLS connection bypass via unhandled callback exception in settlsextservername_callback

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.

Impact

Affected versions

pyopenssl (>= 0.14.0, < 26.0.0)

Security releases

pyopenssl → 26.0.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade pyopenssl to 26.0.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-27448? CVE-2026-27448 is a low-severity security vulnerability in pyopenssl (pip), affecting versions >= 0.14.0, < 26.0.0. It is fixed in 26.0.0.
  2. Which versions of pyopenssl are affected by CVE-2026-27448? pyopenssl (pip) versions >= 0.14.0, < 26.0.0 is affected.
  3. Is there a fix for CVE-2026-27448? Yes. CVE-2026-27448 is fixed in 26.0.0. Upgrade to this version or later.
  4. Is CVE-2026-27448 exploitable, and should I be worried? Whether CVE-2026-27448 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-27448 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-27448? Upgrade pyopenssl to 26.0.0 or later.

Other vulnerabilities in pyopenssl

Stop the waste.
Protect your environment with Kodem.