Skip to content
Connect AISign inSign up free
CVE-2026-847837.5HighCWE-416

CVE-2026-84783: OpenSSL vulnerability

OpenSSL

Vendor fix available · Affected: OpenSSL · Exploitation: not established

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.13 (13 Nov)

  1. In CISA KEV: not seen
  2. Exploited (reported): not seen
  3. Scanning observed: not seen
  4. Proof of concept public: not seen
  5. Not establishedNothing in the sources we check
0.3%probability of exploitation in the next 30 days
21st percentile
050100

Higher than 21% of scored CVEs

7.5HighCVSS
LowHigh

DescriptionNVD

Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
OpenSSL

Coverage2 articles · 2 outlets

One row per outlet, in order of first report. First in our coverage: SecurityOnline, 29 Sep.

Full timeline
Quiet for 7 weekslast report 30 Sep2 articles2 outlets
29 Sep · SecurityOnline first24 Oct1 Nov9 NovNow
  • Tue 29 Sep, 20:49 UTC. SecurityOnline, first report. OpenSSL Fixes 14 Flaws as DTLS Bug Risks Memory Leaks.
  • Wed 30 Sep, 07:13 UTC. SecurityWeek, its first report on the story. OpenSSL and WolfSSL Patch Flaws Threatening TLS Authentication.
All coveragerunning total2SecurityOnl…1SecurityWeek130 Sep16 Oct1 NovNow
  • First report
  • Article
  • Running total
Show as table
2 articles about CVE-2026-84783 from 2 outlets
Published (UTC)OutletHeadline
29 Sep 20:49SecurityOnlineOpenSSL Fixes 14 Flaws as DTLS Bug Risks Memory Leaks
30 Sep 07:13SecurityWeekOpenSSL and WolfSSL Patch Flaws Threatening TLS Authentication
  1. OpenSSL Fixes 14 Flaws as DTLS Bug Risks Memory Leaks
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References