GHSA-h2cc-wx97-xp8v · 深刻度： high — Issue summary: An uncommon configuration of clients performing DANE TLSA-based server...
Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.
総合評価: CVE-2026-28387 は中リスク（50.3/100）。CVSS 深刻度は高。悪用される可能性が高い（EPSS 0.76%、51 パーセンタイル） 推奨対応: 影響資産を整理し、修補計画に組み込んでください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-07-15 | 0.63% | 0.76% | +0.12% |
| 2 | 2026-06-15 | 0.02% | 0.63% | +0.61% |
| 3 | 2026-04-08 | — | 0.02% | — |
EPSS の全履歴 （全 3 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 8.1 | 3.1 | HIGH |
|
2.2 | 5.9 | [email protected] |
| 8.1 | 3.1 | HIGH |
|
2.2 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
GHSA-h2cc-wx97-xp8v · 深刻度： high — Issue summary: An uncommon configuration of clients performing DANE TLSA-based server...
| vendor | priority | summary | link |
|---|---|---|---|
alpine
|
— | CVE-2026-28387: 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-28387 |
debian
|
not yet assigned | CVE-2026-28387 not yet assigned 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-28387 |
redhat
|
low | — | https://access.redhat.com/security/cve/CVE-2026-28387 |
suse
|
medium | CVE-2026-28387 severity moderate: SUSE including 395 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, …), 749 product×package rows across 97 product lines (Container private-registry/harbor-core, Container private-registry/harbor-exporter, … (97 product lines)): Fixed 416, Known Affected 231, Known Not Affected 87, First Fixed 15. | https://www.suse.com/security/cve/CVE-2026-28387/ |
ubuntu
|
low | CVE-2026-28387 low priority: Ubuntu including 5 source packages (edk2, nodejs, openssl, openssl-fips, openssl1.0), 37 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): needs-triage 13, DNE 8, not-affected 8, released 7, needed 1. | https://ubuntu.com/security/CVE-2026-28387 |
| ベンダー | 製品 | バージョン | 生の CPE |
|---|---|---|---|
| openssl | openssl | >= 1.1.1, < 1.1.1zg | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* |
| 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:*:*:*:*:*:*:*:* |