CVE-2026-75805
- Source
- https://cve.org/CVERecord?id=CVE-2026-75805
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-75805.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-75805
- Downstream
- Published
- 2026-09-29T15:32:20Z
- Modified
- 2026-09-30T03:49:55Z
- Severity
-
- 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CVSS Calculator
- Summary
- NULL Pointer Dereference in CMP Client Revocation Response Handling
- Details
-
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 ' 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.
- Database specific
{ "cna_assigner": "openssl", "cwe_ids": [ "CWE-476" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/75xxx/CVE-2026-75805.json", "unresolved_ranges": [ { "extracted_events": [ { "introduced": "3.0.0" }, { "fixed": "3.0.23" } ], "source": "AFFECTED_FIELD" } ] }- References
-
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/75xxx/CVE-2026-75805.json
- https://github.com/openssl/openssl/commit/7588db7fef14209c3caa3a101d11a02006b19166
- https://github.com/openssl/openssl/commit/7ca0ccb5172a577e9b87267d77bfe21e5481a5e7
- https://github.com/openssl/openssl/commit/9eb2a8a9b86136cdb39d6d7d50644dd66941cdc3
- https://github.com/openssl/openssl/commit/abf02872a4b71767ecc72293424420f5b009190f
- https://nvd.nist.gov/vuln/detail/CVE-2026-75805
- https://openssl-library.org/news/secadv/20260929.txt
Affected packages
Git / github.com/openssl/openssl
Affected ranges
- Type
- GIT
- Repo
- https://github.com/openssl/openssl
- Events
-
IntroducedFixedIntroducedFixedIntroducedFixedIntroducedFixed
- Database specific
-
Show details
{ "extracted_events": [ { "introduced": "4.0.0" }, { "fixed": "4.0.3" }, { "introduced": "3.6.0" }, { "fixed": "3.6.5" }, { "introduced": "3.5.0" }, { "fixed": "3.5.9" }, { "introduced": "3.4.0" }, { "fixed": "3.4.8" } ], "source": "AFFECTED_FIELD" }