CVE-2026-35189

Excessive Memory Allocation in Relative CRLDP Processing

MEDIUM
5.3
CVSS Score
Published: September 29, 2026 at 03:32 PM UTC
Updated: October 8, 2026 at 01:01 AM UTC
1 product affected across 1 vendorOpenSSL

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.2 ≤ v < 1.0.2zs1.1.1 ≤ v < 1.1.1zj3.0.0 ≤ v < 3.0.233.4.0 ≤ v < 3.4.83.5.0 ≤ v < 3.5.93.6.0 ≤ v < 3.6.54.0.0 ≤ v < 4.0.31.0.21.1.13.0.03.4.03.5.03.6.04.0.0
Affected range stops below 1.0.2zs, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1zj, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card