OpenSSL · OpenSSL · published 2026-04-07

CVE-2026-31790Incorrect Failure Handling in RSA KEM RSASVE Encapsulation

This month EPSS 1.0% with high severity (CVSS 7.5).

CVE-2026-31790 is not known to be exploited in the wild. EPSS estimates a 1.0% chance of exploitation in the next 30 days, higher than 65% of all CVEs. This OpenSSL vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 3.6.2, 3.5.6, 3.4.5, 3.3.7 (+3 more). Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in OpenSSL 3.6.2, 3.5.6, 3.4.5, 3.3.7, 3.0.20, 1.1.1zg, 1.0.2zp.

Patch events

  1. This monthSecurity release

    Crypto libraryOpenSSL

    OpenSSL security fixes: 7 CVEs

    Upgrade to 3.6.23.5.63.4.53.3.73.0.201.1.1zg1.0.2zp

    Why: CVE-2026-31790: EPSS 1.0% with high severity (CVSS 7.5).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)1.0% (65th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →