Vulnerability · Published Aug 25, 2026 · Assigned by openssl
CVE-2026-14457RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate
High 7.5
In plain English
A high-severity null pointer dereference in OpenSSL from OpenSSL. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.2% (higher than 67% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:10 | openssl | 1:3.5.8-1.el10_2.alma.1 | ALSA-2026:67154 |
| AlmaLinux:9 | openssl | 1:3.5.8-1.el9_8 | ALSA-2026:67165 |
| AlmaLinux:10 | openssl-devel | 1:3.5.8-1.el10_2.alma.1 | ALSA-2026:67154 |
| AlmaLinux:9 | openssl-devel | 1:3.5.8-1.el9_8 | ALSA-2026:67165 |
| AlmaLinux:10 | openssl-libs | 1:3.5.8-1.el10_2.alma.1 | ALSA-2026:67154 |
| AlmaLinux:9 | openssl-libs | 1:3.5.8-1.el9_8 | ALSA-2026:67165 |
| AlmaLinux:10 | openssl-perl | 1:3.5.8-1.el10_2.alma.1 | ALSA-2026:67154 |
| AlmaLinux:9 | openssl-perl | 1:3.5.8-1.el9_8 | ALSA-2026:67165 |
| Alpine:v3.22 | openssl | 3.5.8-r0 | ALPINE-CVE-2026-14457 |
| Alpine:v3.23 | openssl | 3.5.8-r0 | ALPINE-CVE-2026-14457 |
| Alpine:v3.24 | openssl | 3.5.8-r0 | ALPINE-CVE-2026-14457 |
| Debian:13 | openssl | 3.5.7-1~deb13u2 | DEBIAN-CVE-2026-14457 |
| Debian:14 | openssl | 3.6.4-1 | DEBIAN-CVE-2026-14457 |
| Rocky Linux:10 | openssl | 1:3.5.8-1.el10_2 | RLSA-2026:67154 |
| Rocky Linux:9 | openssl | 1:3.5.8-1.el9_8 | RLSA-2026:67165 |
| Ubuntu:26.04:LTS | edk2 | no fix listed | UBUNTU-CVE-2026-14457 |
| Ubuntu:26.10 | edk2 | no fix listed | UBUNTU-CVE-2026-14457 |
| Ubuntu:26.04:LTS | edk2-hwe | no fix listed | UBUNTU-CVE-2026-14457 |
| Ubuntu:26.10 | edk2-hwe | no fix listed | UBUNTU-CVE-2026-14457 |
| Ubuntu:22.04:LTS | openssl | 3.0.2-0ubuntu1.29 | USN-8678-1 |
| Ubuntu:24.04:LTS | openssl | 3.0.13-0ubuntu3.15 | USN-8678-1 |
| Ubuntu:26.04:LTS | openssl | 3.5.5-1ubuntu3.4 | USN-8678-1 |
| Ubuntu:26.04:LTS | openssl | 3.5.5-1ubuntu3.4 | UBUNTU-CVE-2026-14457 |
Affected products (as reported)
Weakness: CWE-476 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
- OpenSSL Advisory vendor-advisory
- 4.0.2 git commit patch
- 3.6.4 git commit patch
- 3.5.8 git commit patch
- 3.4.7 git commit patch