Cloudanix VulnDB

CVE-2026-14457

High · 7.5

CVSS

7.5

EPSS

1.2%

Published

Aug 25, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A configuration mistake in the encryption library used by many servers can let remote attackers crash those services simply by starting a connection the wrong way.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Denial Of Service
Component
Library
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

NULL pointer dereference in OpenSSL TLS handshake handling when RFC7250 Raw Public Key mode is enabled with only a private key configured and the peer sends the signature_algorithms_cert extension, resulting in process abort.

Why it matters to the business

Remote unauthenticated attackers can trigger denial-of-service crashes against servers or clients using the affected key-only RPK configuration, disrupting TLS-protected services until restart; urgency is elevated for Red Hat environments because fixed builds are already published and the library is widely depended upon.

How an attack unfolds

An attacker initiates a TLS connection to a vulnerable server or client configured for Raw Public Keys with only a private key and no certificate; during the handshake the attacker includes the normally-omitted signature_algorithms_cert extension, causing the NULL dereference and immediate abort with no further interaction required.

How to fix it

Upgrade affected packages to the following fixed versions: openssl (el10) 3.5.8-1.el10_2, openssl (el9) 3.5.8-1.el9_8, openssl3-main 3.5.8-0.1.hum1, openssl-main 3.5.8-0.1.hum1, rhui5/cds kubernetes-rhel9:1789479916. Where immediate upgrade is not possible, configure a matching certificate alongside the private key to avoid the vulnerable code path.

How to confirm the fix worked

Verify installed package versions match or exceed the listed fixed releases; confirm that key-only RPK configurations now complete handshakes when the signature_algorithms_cert extension is present; monitor process stability under synthetic handshake tests that include the extension.

Typical attack path

  1. Establish TCP connection to target TLS endpoint
  2. Send ClientHello or ServerHello containing signature_algorithms_cert extension while RPK-only private-key config is active
  3. Trigger NULL pointer dereference inside extension processing code
  4. Force process termination and service outage

How to detect it

Search application and system logs for sudden OpenSSL process aborts or segmentation faults occurring during TLS handshake phases; correlate with network flows that carry TLS ClientHello or ServerHello messages containing the signature_algorithms_cert extension.

What your security team should do

  • Apply the listed Red Hat security updates within the next maintenance window
  • Audit all TLS endpoints for key-only RPK configurations and either add matching certificates or upgrade
  • Add OpenSSL version checks to continuous compliance scanning
  • Review TLS handshake error and crash logs for sudden increases in abort events

The 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.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities