CVE-2026-28388

NULL Pointer Dereference When Processing a Delta CRL

HIGH
7.5
CVSS Score
Published: April 7, 2026 at 10:00 PM UTC
Updated: October 15, 2026 at 01:15 AM UTC
3 products affected across 2 vendorsOpenSSLSIMATIC S7-1500 TM MFPSIMATIC CN 4100

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
HIGH7.5
Exploit prediction
EPSS 0.9%
SSVC
No known exploit

Description

Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL 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.2zp1.1.1 ≤ v < 1.1.1zg3.0.0 ≤ v < 3.0.203.3.0 ≤ v < 3.3.73.4.0 ≤ v < 3.4.53.5.0 ≤ v < 3.5.63.6.0 ≤ v < 3.6.21.0.21.1.13.0.03.3.03.4.03.5.03.6.0
Affected range stops below 1.0.2zp, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1zg, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.2, so it looks safe — our inference, not a vendor statement
v < V5.0
Affected range stops below V5.0, 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

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

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