cve.bz

CVE-2026-72897 openssl openssl: Out-of-bounds Write

7.5 highEPSS 0.4%Fix available

High (7.5) in openssl openssl. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-72897 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72897?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72897?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72897 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenSSLfrom 4.0.0 before 4.0.3
OpenSSLfrom 3.6.0 before 3.6.5
OpenSSLfrom 3.5.0 before 3.5.9
OpenSSLfrom 3.4.0 before 3.4.8

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13openssl3.5.7-1~deb13u3DEBIAN-CVE-2026-72897
Debian14openssl3.6.5-1DEBIAN-CVE-2026-72897
Ubuntu22.04:LTSopenssl3.0.2-0ubuntu1.30USN-8847-1
Ubuntu24.04:LTSopenssl3.0.13-0ubuntu3.16USN-8847-1
Ubuntu26.04:LTSopenssl3.5.5-1ubuntu3.6UBUNTU-CVE-2026-72897 USN-8847-1
Ubuntu26.04:LTS, 26.10edk2, edk2-hweno fix listedUBUNTU-CVE-2026-72897
UbuntuPro:22.04:LTSnodejsno fix listedUBUNTU-CVE-2026-72897
Red Hatenterprise_linux:9::appstreamopenssl-perl, openssl-devel, openssl-debuginfo and 2 more1:3.5.9-1.el9_9RHSA-2026:98484
Red Hatenterprise_linux:9::baseosopenssl, openssl-libs, openssl-debuginfo and 2 more1:3.5.9-1.el9_9RHSA-2026:98484
Red Hatenterprise_linux:10.3openssl, openssl-libs, openssl-perl and 4 more1:3.5.9-1.el10_3RHSA-2026:98588
Red Hathummingbird:1openssl, openssl-libs, openssl-perl and 4 more1:3.5.9-0.1.hum1RHSA-2026:74162
Red Hathummingbird:1openssl3, openssl3-libs, openssl3-devel and 1 more1:3.5.9-0.1.hum1RHSA-2026:74166
SUSELinux Enterprise Module for Basesystem 15 SP7openssl-33.5.0-150700.5.53.2SUSE-SU-2026:4414-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0openssl-33.5.0-160000.11.1SUSE-SU-2026:24245-1
SUSELinux Micro 6.2openssl-33.5.0-160000.11.1SUSE-SU-2026:24188-1
openSUSELeap 16.0openssl-33.5.0-160000.11.1openSUSE-SU-2026:22102-1
AlmaLinux9openssl, openssl-libs, openssl-perl and 1 more1:3.5.9-1.el9_9ALSA-2026:98484
AlmaLinux10openssl, openssl-libs, openssl-perl and 1 more1:3.5.9-1.el10_3.alma.1ALSA-2026:98588
Rocky Linux9openssl, openssl-libs, openssl-perl and 4 more1:3.5.9-1.el9_9RLSA-2026:98484
Rocky Linux10openssl, openssl-libs, openssl-perl and 4 more1:3.5.9-1.el10_3RLSA-2026:98588
Alpinev3.21openssl3.3.7-r2ALPINE-CVE-2026-72897
Azure Linux3cloud-hypervisorno fix listedAZL-105471
Azure Linux3kata-containersno fix listedAZL-105498
Azure Linux3openssl3.3.7-7AZL-105588
Azure Linux3openvmmno fix listedAZL-105633
Azure Linux3rustno fix listedAZL-105825 AZL-105873
Alpaquita25, streamopenssl3.5.9-r0BELL-CVE-2026-72897
BellSoft Hardened Containers25, streamopenssl3.5.9-r0BELL-CVE-2026-72897

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue is rated Moderate because a TLS server that calls SSL_set_SSL_CTX() mid-handshake can suffer a small out-of-bounds read/write if the replacement context exposes more provider signature algorithms than the original, which may crash the process. Applications that never call SSL_set_SSL_CTX() are not affected; the configuration is uncommon and not default.

Red Hat's mitigation

Avoid calling SSL_set_SSL_CTX() during an active handshake unless required (for example SNI virtual hosts). Ensure original and replacement SSL_CTX instances are created with consistent provider/signature-algorithm configuration.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10openssl-1:3.5.9-1.el10_3Fixed 2026-11-11RHSA-2026:98588
Red Hat Hardened Imagesopenssl-main-3.5.9-0.1.hum1Fixed 2026-09-30RHSA-2026:74162
Red Hat Hardened Imagesopenssl3-main-3.5.9-0.1.hum1Fixed 2026-09-30RHSA-2026:74166
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Fix deferred
Red Hat Enterprise Linux 10edk2Affected
Red Hat Enterprise Linux 10shimAffected
Red Hat Enterprise Linux 10shim-unsigned-aarch64Affected
Red Hat Enterprise Linux 10shim-unsigned-x64Affected
Red Hat Enterprise Linux 6opensslNot affected
Red Hat Enterprise Linux 7opensslNot affected
Red Hat Enterprise Linux 7ovmfNot affected
Red Hat Enterprise Linux 7shim-signedNot affected
Red Hat Enterprise Linux 8compat-openssl10Not affected
Red Hat Enterprise Linux 8edk2Not affected
Red Hat Enterprise Linux 8mingw-opensslNot affected
Red Hat Enterprise Linux 8opensslNot affected
Red Hat Enterprise Linux 8shimNot affected
Red Hat Enterprise Linux 8shim-unsigned-aarch64Not affected
Red Hat Enterprise Linux 8shim-unsigned-x64Not affected
Red Hat Enterprise Linux 9compat-openssl11Affected
44 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-72897.

References

Check your stackJSON