RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate (CVE-2026-14457) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-14457

RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate

Answer in brief

CVE-2026-14457 records a Unknown severity vulnerability in RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate. The current sources do not mark it as known exploited. The current feed maps OpenSSL/OpenSSL (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 25, 2026Updated Aug 25, 2026Source checked Aug 25, 2026First seen by HOL Aug 25, 2026Material review Aug 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenSSL/OpenSSL (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenSSL/OpenSSLgeneric	>=4.0.0 <4.0.2 \|\| >=3.6.0 <3.6.4 \|\| >=3.5.0 <3.5.8 \|\| >=3.4.0 <3.4.7	4.0.2, 3.6.4, 3.5.8, 3.4.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenSSL/OpenSSL.
Review the reported fix. Update OpenSSL/OpenSSL to 4.0.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.