CVE-2026-35189: Excessive Memory Allocation in Relative CRLDP Processing
Fixed in Debian 12/13, Alpine 3.21 · Affected: OpenSSL · Exploitation: not established
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.09 (9 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 24% of scored CVEs
DescriptionNVD
Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- Red Hat Enterprise Linux 10Affected, no fix releasedchecked 10 Nov 04:00 UTC
- Red Hat Enterprise Linux 9Affected, no fix releasedchecked 10 Nov 04:00 UTC
- Red Hat Enterprise Linux 8Affected, no fix releasedchecked 10 Nov 04:00 UTC
- Debian 13Fixed in openssl 3.5.7-1~deb13u3 (DSA-6531-1)checked 10 Nov 04:00 UTC
- Debian 12Fixed in openssl 3.0.22-1~deb12u2 (DLA-4859-1)checked 10 Nov 04:00 UTC
- SUSE Linux Enterprise Server 16.1Not affectedchecked 10 Nov 04:00 UTC
- SUSE Linux Enterprise Server 16.0Not affectedchecked 10 Nov 04:00 UTC
- SUSE Linux Enterprise Server 15 SP7Not affectedchecked 10 Nov 04:00 UTC
- openSUSE Leap 16.1Not affectedchecked 10 Nov 04:00 UTC
- openSUSE Leap 16.0Not affectedchecked 10 Nov 04:00 UTC
- Alpine Linux 3.21Fixed in openssl-3.3.7-r2checked 10 Nov 04:00 UTC
What changed
Alpine status tracked since 10 Nov 2026. Debian status tracked since 10 Nov 2026. Red Hat status tracked since 10 Nov 2026. SUSE status tracked since 10 Nov 2026.
- Seen in Alpine’s tracker on 10 Nov: Alpine 3.21 fixed in openssl-3.3.7-r2 Alpine
- Seen in Debian’s tracker on 10 Nov: Debian 12 fixed in openssl 3.0.22-1~deb12u2 (DLA-4859-1) Debian
- Seen in Debian’s tracker on 10 Nov: Debian 13 fixed in openssl 3.5.7-1~deb13u3 (DSA-6531-1) Debian
- Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 7 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 8 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
- SUSE’s tracker lists openSUSE Leap 16.0 as not affected SUSE
- SUSE’s tracker lists openSUSE Leap 16.1 as not affected SUSE
- SUSE’s tracker lists SLES 12 SP5 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP1 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP2 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP3 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP4 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP5 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP6 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP7 as not affected SUSE
- SUSE’s tracker lists SLES 16.0 as not affected SUSE
- SUSE’s tracker lists SLES 16.1 as not affected SUSE
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 10 Nov.
- Progress fixes five WS_FTP Server flaws exposing sensitive dataSecurityOnline · first in our coverage · mentions it in passing
New articles also arrive in the RSS feed.