CVE-2026-72897: Out-of-Bounds Access After SSL_set_SSL_CTX() During a Handshake
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: OpenSSL OpenSSL 3.4.8, 3.5.9, 3.6.5; azl3 openssl 3.3.7-6 on Azure Linux 3.0 3.3.7-7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to OpenSSL OpenSSL 3.4.8, 3.5.9, 3.6.5; azl3 openssl 3.3.7-6 on Azure Linux 3.0 3.3.7-7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 29, 2026
- Updated
- Oct 8, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-787
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 4.0.0 and later · before 4.0.3affected · semver
- 3.6.0 and later · before 3.6.5affected · semver
- 3.5.0 and later · before 3.5.9affected · semver
- 3.4.0 and later · before 3.4.8affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl3.4.0 and later · before 3.4.8
- openssl openssl3.5.0 and later · before 3.5.9
- openssl openssl3.6.0 and later · before 3.6.5
- openssl openssl4.0.0 and later · before 4.0.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | openssl | from 3.4.0 · before 3.3.7-r2 | 3.3.7-r2 |
| Debian:13 | openssl | before 3.5.7-1~deb13u3 | 3.5.7-1~deb13u3 |
| Debian:14 | openssl | before 3.6.5-1 | 3.6.5-1 |
| openSUSE:Leap 16.0 | openssl-3 | before 3.5.0-160000.11.1 | 3.5.0-160000.11.1 |
| Red Hat:enterprise_linux:10.3 | openssl | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:10.3 | openssl-debuginfo | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:10.3 | openssl-debugsource | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:10.3 | openssl-devel | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:10.3 | openssl-libs | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:10.3 | openssl-libs-debuginfo | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:10.3 | openssl-perl | before 1:3.5.9-1.el10_3 | 1:3.5.9-1.el10_3 |
| Red Hat:enterprise_linux:9::appstream | openssl-debuginfo | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:enterprise_linux:9::appstream | openssl-debugsource | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:enterprise_linux:9::appstream | openssl-devel | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:enterprise_linux:9::appstream | openssl-libs-debuginfo | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:enterprise_linux:9::appstream | openssl-perl | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:enterprise_linux:9::baseos | openssl | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:enterprise_linux:9::baseos | openssl-libs | before 1:3.5.9-1.el9_9 | 1:3.5.9-1.el9_9 |
| Red Hat:hummingbird:1 | openssl | before 1:3.5.9-0.1.hum1 | 1:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-config-fips | before 1:3.5.9-0.1.hum1 | 1:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-devel | before 1:3.5.9-0.1.hum1 | 1:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-devel-engine | before 1:3.5.9-0.1.hum1 | 1:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-fips-provider-upstream | before 1:3.5.9-0.1.hum1 | 1:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-libs | before 1:3.5.9-0.1.hum1 | 1:3.5.9-0.1.hum1 |
+21
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2026-54873Sep 29, 2026 · QUIC STREAM Fragment Metadata DoS30Monitor
- ← EarlierCVE-2026-54875Sep 29, 2026 · Non-Constant-Time SM2 Scalar Multiplication on ARM64 and RISC-V14Monitor
- Later →CVE-2026-75804Sep 29, 2026 · QUIC Connection-Level Flow Control is Not Enforced for Streams21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.4.8 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.5.9 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.6.5 | Vendor (CNA) |
| OpenSSL OpenSSL | 4.0.3 | Vendor (CNA) |
| azl3 openssl 3.3.7-6 on Azure Linux 3.0 | 3.3.7-7 · Release Notes | Microsoft (MSRC) |
| alpine:openssl | 3.3.7-r2 · Alpine:v3.21 | Package registry (OSV) |
| debian:openssl | 3.5.7-1~deb13u3 · Debian:13 | Package registry (OSV) |
| opensuse:openssl-3 | 3.5.0-160000.11.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:openssl | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-config-fips | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-config-fips | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.5.9-1.el9_9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-devel | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel-engine | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel-engine | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-fips-provider-upstream | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-fips-provider-upstream | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-libs | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-libs | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-perl | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-perl | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3 | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3 | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel-engine | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel-engine | 1:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-libs | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+10
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+48 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Filipe Casal (TrailBits)reporter
- Brandon Luoreporter
- Luigino Camastra (Aisle Research)reporter
- Matt Caswellremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-15467245 days apartStack buffer overflow in CMS (Auth)EnvelopedData parsing57Plan
- CVE-2026-31789175 days apartHeap Buffer Overflow in Hexadecimal Conversion39Monitor
- CVE-2026-7383112 days apartPossible Heap Buffer Overflow in ASN.1 Multibyte String Conversion32Monitor
- CVE-2026-6307235 days apartHeap Buffer Overflow in CMS Key Unwrapping30Monitor
- CVE-2025-69419245 days apartOut of bounds write in PKCS12_get_friendlyname() UTF-8 conversion29Monitor
- CVE-2025-68160245 days apartHeap out-of-bounds write in BIO_f_linebuffer on short writes18Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1218 · Sep 30, 2026(OpenSSL Güvenlik Zafiyeti)
Not on record for this CVE: public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
- CVSS— → 7.5
- Severity— → high
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.