CVE-2026-42765
Last modified
CVE-2026-42765 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.42% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openssl | Openssl | >= 3.6.0, < 3.6.3 |
| Openssl | Openssl | 4.0.0 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-42765?
How severe is CVE-2026-42765?
How do I fix CVE-2026-42765?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-4276LibreChat RAG API, version 0.7.0, contains a log-injection v…7.5
- CVE-2026-42760Authentication Bypass Using an Alternate Path or Channel vul…7.5
- CVE-2026-42761Improper Neutralization of Special Elements used in an SQL C…9.3
- CVE-2026-42762Improper Neutralization of Input During Web Page Generation …7.1
- CVE-2026-42763Missing Authorization vulnerability in SePay team SePay Gate…6.5
- CVE-2026-42764Issue summary: Receiving a QUIC initial packet with an inval…7.5
- CVE-2026-42766Issue summary: A specially crafted password-encrypted CMS me…5.9
- CVE-2026-42767Issue summary: An attacker-controlled CMP (Certificate Manag…5.9
- CVE-2026-42768Issue summary: The CMS_decrypt and PKCS7_decrypt functions a…3.7
- CVE-2026-42769Issue Summary: An error in the callback used to verify the c…5.3
- CVE-2026-4277An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.…9.8
- CVE-2026-42770Issue summary: When EVP_PKEY_derive_set_peer() is called wit…3.7
Are you affected by CVE-2026-42765?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
