CVE-2026-14457

*** Pendiente de traducción *** Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs)<br /> enabled, and only the private key (with no associated certificate) configured locally,<br /> a NULL pointer dereference may occur when the remote peer solicits raw public keys and<br /> also sends the typically omitted "signature_algorithms_cert" TLS extension.<br /> <br /> Impact summary: The impact is limited to a possible Denial of Service as a result of<br /> an application abort, no data disclosure or remote command execution are possible.<br /> <br /> CWE: CWE-476: NULL Pointer Dereference<br /> <br /> Description: While a passing comment in sample code in the documentation suggests<br /> that key-only RPK configurations are supported, the best-practice RPK configuration<br /> is to always configure a corresponding certificate (possibly self-signed or<br /> signed by any convenient CA).<br /> <br /> When the private key is configured along with a matching certificate, the<br /> "signature_algorithms_cert" extension is handled reliably even without the<br /> fix, and peer clients or servers that don&amp;#39;t support raw public keys may be<br /> able to complete a TLS connection by pinning or verifying the corresponding<br /> certificate or its public key.<br /> <br /> Deployments that prefer to configure just a private key with no certificate<br /> need to upgrade to an updated release as noted below.<br /> <br /> FIPS impact: no<br /> <br /> No FIPS modules are affected by this issue, as the SSL protocol implementation<br /> is outside the OpenSSL FIPS module boundary.