7.5

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

Modified
AliasesALPINE-CVE-2026-31790RHSA-2026:19218RHSA-2026:27744
Published 07-04-2026Last modified 12-05-2026

Vulnerability summary

CVE-2026-31790 is a high (CVSS 7.5) vulnerability in openssl. EPSS estimates a 1.03% chance of exploitation in the next 30 days, higher than 63.7% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
1.03%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 22 · Related 16

Timeline

  1. 07-04-2026
    PublishedVulnerability first disclosed.
  2. 12-05-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

8 scores · 8 sources · 1 version

EPSS trend

Probability

1.03%

Chance of exploitation in the next 30 days

Percentile

64%

Versus all other CVEs

30-day change

No change 0.00 pp

From 1.03% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Redhat12 products
  • openssl< 1:3.5.5-2.el9_8
  • openssl-debuginfo< 1:3.5.5-2.el9_8
  • openssl-debugsource< 1:3.5.5-2.el9_8
  • openssl-devel< 1:3.5.5-2.el9_8
  • openssl-fips-provider< 0:3.0.7-11.el9_8 | < 0:3.0.7-11.el10_0 | < 0:3.0.7-11.el10_2 | < 0:3.0.7-1.2.hum1 | < 0:3.0.7-11.el9_0
Chainguard11 products
  • libcrypto3< 3.6.2-r0
  • libcrypto3-2.34< 3.6.2-r0
  • openssl< 3.6.2-r0
  • openssl-3.5< 3.5.6-r0
  • openssl-3.5-libcrypto< 3.5.6-r0
Ubuntu4 products
  • edk2All versions (No fix recorded)
  • edk2-hweAll versions (No fix recorded)
  • openssl< 3.0.2-0ubuntu1.23 | All versions (No fix recorded) | < 3.0.13-0ubuntu3.9 | < 3.5.3-1ubuntu3.3 | < 3.5.5-1ubuntu3
  • openssl-fipsAll versions (No fix recorded) | < 3.0.13-0ubuntu3.12+Fips1
Wolfi2 products
  • libcrypto3< 3.6.2-r0
  • openssl< 3.6.2-r0
Alpine1 product
  • openssl≥ 3.0.0, < 3.3.7-r0 | ≥ 3.0.0, < 3.5.6-r0
Debian1 product
  • openssl< 3.0.19-1~deb12u2 | < 3.5.5-1~deb13u2 | < 3.6.2-1
Openssl1 product
  • openssl≥ 3.0.0, < 3.0.20 | ≥ 3.3.0, < 3.3.7 | ≥ 3.4.0, < 3.4.5 | ≥ 3.5.0, < 3.5.6 | ≥ 3.6.0, < 3.6.2

7 vendors · 32 products

References

32 links
Show all 32 references