CVE Tools

CVE-2026-84786

Possible NULL Dereference in Non-SMTP DANE Clients

No known exploitation. EPSS puts it in the 1st percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • OpenSSLAffected: ≥ 4.1.0, < 4.1.1Upgrade to: 4.1.1Affected: ≥ 4.0.0, < 4.0.4Upgrade to: 4.0.4Affected: ≥ 3.5.0, < 3.5.10Upgrade to: 3.5.10Affected: ≥ 3.0.0, < 3.0.24Upgrade to: 3.0.24 + 1 more branchStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. Impact summary: The impact is limited to a client crash (potential Denial of Service). CWE: CWE-476: NULL Pointer Dereference Description: A DANE-enabled TLS client that supports TLSA records with at least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2) usage may crash by dereferencing a NULL pointer if the server claims a trusted CA's certificate to be its end-entity certificate and has an unusual mix of associated TLSA records. DANE SMTP clients should not be affected since only the DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable in SMTP. For example, the Postfix MTA is not affected, while the Exim MTA does not at present use OpenSSL's DANE implementation. Use of DANE in validation of RFC7250 raw public keys (RPKs) is also unaffected, as these only use DANE-EE(3) TLSA records. Only applications that support combining the DANE PKI with a traditional PKI are potentially affected. A DANE-enabled browser or similar, that uses OpenSSL's DANE API could be affected. FIPS impact: no The DANE API is outside the FIPS module boundary.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS1st
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

<0.1% chance of exploitation activity in the next 30 days, which ranks it in the 1st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 2 days, from the signal feeds we watch.

  1. Record updated
  2. Record updated
  3. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for OpenSSL, not every advisory.