OpenSSL · OpenSSL · published 2026-09-29
CVE-2026-75805NULL Pointer Dereference in CMP Client Revocation Response Handling
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-75805 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 31% of all CVEs. This OpenSSL vulnerability: CVSS 5.3 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 4.0.3, 3.6.5, 3.5.9, 3.4.8 (+3 more); patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 4.0.3, 3.6.5, 3.5.9, 3.4.8, 3.0.23, 1.1.1zj, 1.0.2zs.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | openssl | Fixed in 3.5.7-1~deb13u3 |
| 12 bookworm | openssl | Fixed in 3.0.22-1~deb12u2 | |
| Ubuntu (+3 more packages) | 26.04 LTS | openssl | Fixed in 3.5.5-1ubuntu3.6 |
| 24.04 LTS | openssl | Fixed in 3.0.13-0ubuntu3.16 | |
| 22.04 LTS | openssl | Fixed in 3.0.2-0ubuntu1.30 | |
| Red Hat Enterprise Linux (+17 more packages) | RHEL 10 | openssl | Fixed in 3.5.9-1.el10_3 RHSA-2026:98588 |
| RHEL 9 | openssl | Fixed in 3.5.9-1.el9_9 RHSA-2026:98484 | |
| RHEL 8 | openssl | Not affected | |
| RHEL 7 | openssl | Not affected | |
| RHEL 6 | openssl | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Crypto libraryOpenSSL
OpenSSL security fixes: 14 CVEs
Upgrade to
4.0.33.6.53.5.93.4.83.0.231.1.1zj1.0.2zsWhy: Vendor security release for server software (most severe: CVE-2026-84782).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (32th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- OpenSSL OpenSSL
4.0.0to before4.0.3(affected)3.6.0to before3.6.5(affected)3.5.0to before3.5.9(affected)3.4.0to before3.4.8(affected)3.0.0to before3.0.23(affected)
Description (from the CVE record)#
Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.
Quoted from the CVE Program record.