Issue summary: The first concurrent use of the same X.509 certificate by
\nseveral threads may cause its cached extension data to be freed while
\nanother thread is still using it.<\/p>\n
Impact summary: A remote, unauthenticated peer could crash a multi-threaded
\nTLS client, or a multi-threaded TLS server that requests client
\ncertificates, if the first certificate chains built to the same trusted CA
\ncertificate are built by several connections at the same time. This is a
\nuse-after-free read, which is likely to crash the process, resulting in a
\nDenial of Service.<\/p>\n
CWE: CWE-416: Use After Free<\/p>\n
Description: OpenSSL caches the decoded values of a certificate’s X.509v3
\nextensions inside the X509 object the first time they are needed. In
\nOpenSSL 4.0 this cache is built in two phases: the extension values are
\ncomputed while holding a read lock on the certificate, and the results are
\nthen installed into the certificate under a write lock. Because a read lock
\ndoes not exclude other readers, several threads can compute the cache for
\nthe same certificate at the same time. Each thread that subsequently
\nacquires the write lock installs its own results and frees the values
\ninstalled by the thread before it, even though that earlier thread has
\nalready marked the cache as complete and may have returned pointers into it
\nto its caller. A caller still using those pointers then reads freed memory.<\/p>\n
Any certificate shared between threads is exposed the first time its
\nextensions are decoded. In TLS the certificates at risk are the trusted CA
\ncertificates supplied for chain verification, by whatever means, since these
\nare shared by every connection and their extensions are decoded and cached
\nthe first time a chain is built to them. Certificates sent by the peer are
\ndecoded separately for each connection and are not shared, so they are not
\naffected. In a TLS client verifying server certificates, or a TLS server
\nthat requests and verifies client certificates, the use-after-free could
\nonly occur if the first chains built to the same trusted CA are built by
\nseveral connections at the same time.<\/p>\n
FIPS impact: no
\nThe FIPS module is not affected as X.509 certificate handling is outside
\nof the OpenSSL FIPS module boundary.<\/p>\n
OpenSSL 4.0 is vulnerable to this issue.<\/p>\n
OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.<\/p>\n
OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3.<\/p>\n
This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and
\nindependently in a public report on 31 August 2026 by aydinmercan.<\/p>\n
The fix has been developed by Bob Beck.<\/p>\n
— cut (non-publishing metadata for internal use) —
\nReported by: Tim Becker (Xint.io), aydinmercan
\nFixed by: Bob Beck<\/p>\n","protected":false},"excerpt":{"rendered":"
Issue summary: The first concurrent use of the same X.509 certificate by
\nseveral threads may cause its cached extension data to be freed while
\nanother thread is still using it.<\/p>\n
Impact summary: A remo<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-30633","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/30633","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=30633"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=30633"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=30633"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}