CVE-2026-75805NULL Pointer Dereference in CMP Client Revocation Response Handling
Updated under an hour ago ()
Does this affect you?
It affects OpenSSL. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 5.3 MEDIUM (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Weakness (CWE)
- CWE-476
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- openssl
- NVD analysis
- Analyzed
- Record last updated
- Sep 29, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
OpenSSL OpenSSL openssl:openssl (from the name) | from 4.0.0 before 4.0.3; from 3.6.0 before 3.6.5; from 3.5.0 before 3.5.9; from 3.4.0 before 3.4.8; from 3.0.0 before 3.0.23 | CNA record |
openssl openssl openssl:openssl | from 3.0.0 before 3.0.23; from 3.4.0 before 3.4.8; from 3.5.0 before 3.5.9; from 3.6.0 before 3.6.5; from 4.0.0 before 4.0.3 | NVD |
References
- https://openssl-library.org/news/secadv/20260929.txtvendor-advisory
- https://github.com/openssl/openssl/commit/7ca0ccb5172a577e9b87267d77bfe21e5481a5e7patch
- https://github.com/openssl/openssl/commit/7588db7fef14209c3caa3a101d11a02006b19166patch
- https://github.com/openssl/openssl/commit/9eb2a8a9b86136cdb39d6d7d50644dd66941cdc3patch
- https://github.com/openssl/openssl/commit/abf02872a4b71767ecc72293424420f5b009190fpatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.