High 7.5Published Aug 25, 2026

CVE-2026-14457RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate

Updated under an hour ago (2026-10-19 09:20 UTC)

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

Start free and add your stack

Free account, 1 product

Every CVE for OpenSSL

Exploited in the last 30 days

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.

CVSS: 7.5 HIGH (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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: Aug 25, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

OpenSSL OpenSSL openssl:openssl (from the name)	from 4.0.0 before 4.0.2; from 3.6.0 before 3.6.4; from 3.5.0 before 3.5.8; from 3.4.0 before 3.4.7	CNA record
openssl openssl openssl:openssl	from 3.4.0 before 3.4.7; from 3.5.0 before 3.5.8; from 3.6.0 before 3.6.4; from 4.0.0 before 4.0.2	NVD

References

https://openssl-library.org/news/secadv/20260825.txtvendor-advisory
https://github.com/openssl/openssl/commit/dad836b071da6579510c968615848ba03cac593bpatch
https://github.com/openssl/openssl/commit/581aaa0f0a35d214740f0fe1f5283ec41f1212e1patch
https://github.com/openssl/openssl/commit/d0af20478688a6aa2f59d61caa3f82136b181d7fpatch
https://github.com/openssl/openssl/commit/1e8c398db67404babd3e5af999bb6bd86f720c76patch

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.