GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL: raw-public-key endpoints with no certificate abort on a peer-sent signature_algorithms_cert extension

CVE-2026-14457Kernel, userspace & hypervisorcurated

Impact

When an OpenSSL server or client is configured for RFC 7250 raw public keys and has only a private key loaded with no matching certificate, a peer that solicits raw public keys and also sends the normally-omitted signature_algorithms_cert extension triggers a NULL pointer dereference. OpenSSL scopes the impact to denial of service via application abort - no data disclosure, no code execution. The configuration is uncommon: OpenSSL's own guidance is to always pair the private key with a certificate, and doing so makes the extension handling reliable even on unpatched builds. Relevant to a fleet mainly where RPK was chosen deliberately for machine-to-machine links between control-plane components, since the abort takes down the whole process.

Who can reach it

Any peer that can open a TLS connection to the affected endpoint, or any server an affected client connects to. No authentication required. Only key-only RPK configurations are exposed.

What to do

Two options. The cheap one, available now, is to configure a matching certificate alongside the private key - self-signed or signed by any convenient CA - which the advisory states makes signature_algorithms_cert handling reliable without the code fix, and which also lets non-RPK peers connect. The durable one is to upgrade to the fixed OpenSSL release named in the 2026-08-25 advisory and restart every service linked against libssl. The record does not give a fixed version for this CVE; read it off the advisory.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.