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

Published Apr 7, 2026
·
Updated

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.

Other sources

Potential Use-after-free in DANE Client Code

Microsoft

Affected Software

10 affected componentsFixes available
OpenSSL OpenSSL>=1.1.1<1.1.1zg
OpenSSL OpenSSL>=3.0.0<3.0.20
OpenSSL OpenSSL>=3.3.0<3.3.7
OpenSSL OpenSSL>=3.4.0<3.4.5
OpenSSL OpenSSL>=3.5.0<3.5.6
OpenSSL OpenSSL>=3.6.0<3.6.2
Microsoft azl3 openssl 3.3.5-5<3.3.7-2
3.3.7-2
Microsoft cbl2 openssl 1.1.1k-39<1.1.1k-40
1.1.1k-40
Microsoft azl3 openssl 3.3.5-4<3.3.7-1
3.3.7-1
IBM API Connect<=V10.0.8.0 - V10.0.8.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.3.7-2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.1.1k-40
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.3.7-1

Event History

Apr 7, 2026
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 9, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:02 AM
Affected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-28387?

CVE-2026-28387 is classified as a high severity vulnerability due to the potential for use-after-free and double-free scenarios.

2

What software is affected by CVE-2026-28387?

CVE-2026-28387 affects various versions of OpenSSL, including versions between 1.1.1 and 3.6.2.

3

How do I fix CVE-2026-28387?

To mitigate CVE-2026-28387, it is recommended to upgrade to the latest patched version of OpenSSL provided by your vendor.

4

What type of vulnerability is CVE-2026-28387?

CVE-2026-28387 is a use-after-free vulnerability that can lead to memory corruption.

5

How does CVE-2026-28387 impact DANE TLSA-based server authentication?

CVE-2026-28387 can cause security issues in clients performing DANE TLSA-based server authentication when paired with improper server configurations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203