CVE-2026-84783: OpenSSL vulnerability
Vendor fix available · Affected: OpenSSL · Exploitation: not established
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.13 (13 Nov)
- In CISA KEV: not seen
- Exploited (reported): not seen
- Scanning observed: not seen
- Proof of concept public: not seen
- Not establishedNothing in the sources we check
Higher than 21% of scored CVEs
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.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- OpenSSL
- Published
- September 2026
Coverage2 articles · 2 outlets
One row per outlet, in order of first report. First in our coverage: SecurityOnline, 29 Sep.
- 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.
- First report
- Article
- Running total
Show as tableHide table
| Published (UTC) | Outlet | Headline |
|---|---|---|
| 29 Sep 20:49 | SecurityOnline | OpenSSL Fixes 14 Flaws as DTLS Bug Risks Memory Leaks |
| 30 Sep 07:13 | SecurityWeek | OpenSSL and WolfSSL Patch Flaws Threatening TLS Authentication |
- OpenSSL and WolfSSL Patch Flaws Threatening TLS AuthenticationSecurityWeek · mentions it in passing
- OpenSSL Fixes 14 Flaws as DTLS Bug Risks Memory LeaksSecurityOnline · first in our coverage · mentions it in passing
New articles also arrive in the RSS feed.