Bug 2481889 (CVE-2026-42765) - CVE-2026-42765 openssl: NULL Dereference in Certificate Verification with OCSP Checking
Summary: CVE-2026-42765 openssl: NULL Dereference in Certificate Verification with OCS...
Keywords:
Status: NEW
Alias: CVE-2026-42765
Deadline: 2026-06-09
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-27 14:18 UTC by OSIDB Bzimport
Modified: 2026-07-09 14:28 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-27 14:18:31 UTC
NULL Dereference in Certificate Verification with OCSP Checking

NULL Dereference in Certificate Verification with OCSP Checking (CVE-2026-42765)
Severity: Low

Issue summary: When a partial-chain certificate verification is enabled
together with OCSP response checking for the whole chain, a NULL dereference
will happen if the verified chain does not have a self-signed trusted anchor,
crashing the process.

Impact summary: A NULL pointer dereference can trigger a crash which leads to a
Denial of Service for an application.

When performing OCSP response checking for certificates in the verification
chain, the code always tries to access the next certificate as the issuer.
There is a check for a self-signed certificate. However with the partial
chain verification enabled when the chain does not have a self-signed trusted
anchor, the issuer will be NULL for the last certificate in the chain. A NULL
pointer dereference then happens.

This issue affects only applications which enable both OCSP verification
of the certificate chain (X509_V_FLAG_OCSP_RESP_CHECK_ALL) and partial
chain verification (X509_V_FLAG_PARTIAL_CHAIN) in the certificate
verification. Both flags are disabled by default. For that reason, we have
assigned Low severity to the issue.

No FIPS modules are affected by this issue as the affected code is outside
the OpenSSL FIPS module boundary.

OpenSSL 4.0 and 3.6 are vulnerable to this issue.

OpenSSL 3.5, 3.4, 3.0, 1.1.1, and 1.0.2 are not affected by this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.1.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.3.

This issue was reported by Joshua Rogers (Aisle Research) on 30th March 2026.
The fix was developed by Joshua Rogers (Aisle Research) and Daniel Kubec.


Note You need to log in before you can comment on or make changes to this bug.