8.1

CVE-2026-28387: Potential Use-after-free in DANE Client Code

Modified
AliasesALPINE-CVE-2026-28387UBUNTU-CVE-2026-28387DEBIAN-CVE-2026-28387
Published 07-04-2026Last modified 15-10-2026

Vulnerability summary

CVE-2026-28387 is a high (CVSS 8.1) Use After Free vulnerability in openssl. EPSS estimates a 0.67% chance of exploitation in the next 30 days, higher than 52% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 8.1 (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
8.1/10
010
High · v3.1 (CVE.org)
EPSS score
0.67%
0%100%
Low · -0.27 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 20 · Related 21

Timeline

  1. 07-04-2026
    PublishedVulnerability first disclosed.
  2. 15-10-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

7 scores · 7 sources · 1 version

EPSS trend

Probability

0.67%

Chance of exploitation in the next 30 days

Percentile

52%

Versus all other CVEs

30-day change

Decrease -0.27 pp

From 0.94% 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.

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
Ubuntu5 products
  • edk2All versions (No fix recorded)
  • edk2-hweAll versions (No fix recorded)
  • nodejsAll versions (No fix recorded)
  • openssl< 1.1.1-1ubuntu2.1~18.04.23+esm8 | < 1.1.1-1ubuntu2.fips.2.1~18.04.23.8 | All versions (No fix recorded) | < 1.1.1f-1ubuntu2.24+esm3 | < 1.1.1f-1ubuntu2.fips.24.3 | < 3.0.2-0ubuntu1.23 | < 3.0.2-0ubuntu1.23+Fips1 | < 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≥ 1.1.1, < 3.3.7-r0 | ≥ 1.1.1, < 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.6.0, < 3.6.2 | ≥ 3.5.0, < 3.5.6 | ≥ 3.4.0, < 3.4.5 | ≥ 3.3.0, < 3.3.7 | ≥ 3.0.0, < 3.0.20 | ≥ 1.1.1, < 1.1.1zg

6 vendors · 21 products

References

17 links
Show all 17 references