Is pyopenssl 17.5 vulnerable?

PyPI · 1 release from 17.5.0 to 17.5.0 · latest pyopenssl is 26.4.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. pyopenssl 17.5.0, the last 17.5 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.

Upgrade with:pip install 'pyopenssl>=26.0.0'

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

Advisories affecting pyopenssl 17.5.0

  • LowCVE-2026-27448GHSA-vp96-hxj8-p42416 Mar 2026

    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

Which of your client projects are still on pyopenssl 17.5?

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.