GHSA-vgxx-5xj5-q97x · 深刻度： high — Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key...
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.
総合評価: CVE-2026-31790 は中リスク（51.1/100）。CVSS 深刻度は高。悪用される可能性が高い（EPSS 0.98%、58 パーセンタイル） 推奨対応: 影響資産を整理し、修補計画に組み込んでください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-06-15 | 0.01% | 0.98% | +0.97% |
| 2 | 2026-04-08 | — | 0.01% | — |
EPSS の全履歴 （全 2 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 7.5 | 3.1 | HIGH |
|
3.9 | 3.6 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
GHSA-vgxx-5xj5-q97x · 深刻度： high — Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key...
| vendor | priority | summary | link |
|---|---|---|---|
alpine
|
— | CVE-2026-31790: 1 source package rows (openssl); 5 state rows across 5 repos (3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 5, open 0. | https://security.alpinelinux.org/vuln/CVE-2026-31790 |
debian
|
unimportant | CVE-2026-31790 unimportant priority: Debian including 1 source packages (openssl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. | https://security-tracker.debian.org/tracker/CVE-2026-31790 |
redhat
|
medium | — | https://access.redhat.com/security/cve/CVE-2026-31790 |
suse
|
medium | CVE-2026-31790 severity moderate: SUSE including 379 source package names (1.1.2-2.16:libopenssl3-3.2.3-150700.5.31.1, 1.1.2-2.16:openssl-3-3.2.3-150700.5.31.1, …), 765 product×package rows across 95 product lines (Container private-registry/harbor-core, Container private-registry/harbor-exporter, … (95 product lines)): Fixed 364, Known Affected 231, Known Not Affected 163, First Fixed 7. | https://www.suse.com/security/cve/CVE-2026-31790/ |
ubuntu
|
medium | CVE-2026-31790 medium priority: Ubuntu including 5 source packages (edk2, nodejs, openssl, openssl-fips, openssl1.0), 32 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): not-affected 16, DNE 6, needs-triage 4, released 4, needed 2. | https://ubuntu.com/security/CVE-2026-31790 |
| ベンダー | 製品 | バージョン | 生の CPE |
|---|---|---|---|
| openssl | openssl | >= 3.0.0, < 3.0.20 | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* |
| openssl | openssl | >= 3.3.0, < 3.3.7 | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* |
| openssl | openssl | >= 3.4.0, < 3.4.5 | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* |
| openssl | openssl | >= 3.5.0, < 3.5.6 | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* |
| openssl | openssl | >= 3.6.0, < 3.6.2 | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* |