Skip to main content
CVE-2026-40475VulnerabilityPublished Updated

SUSE · Security update for python-pyOpenSSL

Affects SUSESource GCVE Database

0
Compare

Not known to be exploited · fixed in SUSE package updates : update SUSE when convenient.

Data as of 17 Sep 2026, 03:24 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Patch
Available – fixed in 25.0.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

Apply the security update provided by SUSE for python-pyOpenSSL to resolve CVE-2026-40475. The fixed package version is python313-pyOpenSSL-25.0.0-160000.4.1.noarch for SUSE Linux Enterprise and openSUSE Leap 16.0. Check SUSE advisories for the official patch and update instructions.

Description

A security update for python-pyOpenSSL addresses CVE-2026-40475, which involves improper input handling of null bytes. This flaw can cause silent data truncation and inconsistencies in the security state. The issue affects SUSE Linux Enterprise and openSUSE Leap 16.0 versions of python313-pyOpenSSL-25.0.0. The severity is assessed as medium based on the described impact. No CVSS score is available. No known exploits are reported in the wild.

References

Community reviews

Loading reviews…