CVE-2026-28387

Potential Use-after-free in DANE Client Code

HIGH
8.1
CVSS Score
Published: April 7, 2026 at 10:00 PM UTC
Updated: October 15, 2026 at 01:15 AM UTC
3 products affected across 2 vendorsOpenSSLSIMATIC S7-1500 TM MFPSIMATIC CN 4100

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.1.1 ≤ v < 1.1.1zg3.0.0 ≤ v < 3.0.203.3.0 ≤ v < 3.3.73.4.0 ≤ v < 3.4.53.5.0 ≤ v < 3.5.63.6.0 ≤ v < 3.6.21.1.13.0.03.3.03.4.03.5.03.6.0
Affected range stops below 1.1.1zg, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.2, so it looks safe — our inference, not a vendor statement
v < V5.0
Affected range stops below V5.0, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card