OpenSSL · OpenSSL · published 2026-08-25
CVE-2026-14457RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate
This month EPSS 1.2% with high severity (CVSS 7.5).
CVE-2026-14457 is not known to be exploited in the wild. EPSS estimates a 1.2% chance of exploitation in the next 30 days, higher than 68% of all CVEs. This OpenSSL vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7 (+3 more). Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, 3.0.22, 1.1.1zi, 1.0.2zr.
Patch events
Crypto libraryOpenSSL
OpenSSL security fixes: 9 CVEs
Upgrade to
4.0.23.6.43.5.83.4.73.0.221.1.1zi1.0.2zrWhy: CVE-2026-63073: EPSS 1.1% with high severity (CVSS 9.8).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.2% (69th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | 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.2(affected)3.6.0to before3.6.4(affected)3.5.0to before3.5.8(affected)3.4.0to before3.4.7(affected)
Description (from the CVE record)#
Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted "signature_algorithms_cert" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the "signature_algorithms_cert" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.
Quoted from the CVE Program record.