Syself security assessment
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.
Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how CVE-2026-14457 affects the openssl component those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.
Syself Kubernetes is not affected by CVE-2026-14457 in any of the 4 releases that ship openssl.
Reason: The vulnerable code is never executed.
This flaw can crash a program that uses a rarely enabled key type for encrypted connections in this library. That option is not turned on here, so the flaw is never reached.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| openssl 3.5.7 | Not affected | The vulnerable code is never executed | — | Details |
Scanners such as Trivy and Grype match package versions, so they report CVE-2026-14457 whenever the vulnerable version is present, even when it cannot be exploited. Syself publishes its assessments as a VEX (Vulnerability Exploitability eXchange) document for every release. Pass it to your scanner to drop the findings Syself has assessed as not affected or fixed:
trivy image --vex hetzner-apalla-1-36-v4-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v4-advisory.openvex.json Each assessment applies to the package version it names. A finding stays in the report when the document has no assessment for that package, or when the vulnerability is still affected or under investigation.
Download the OpenVEX document for 1.36 v4The severity shown is the upstream rating of the vulnerability itself. The status is Syself's assessment of whether it can be exploited in the components Syself ships, so a critical vulnerability can still be not affected.
Think this assessment is wrong, or found a vulnerability in Syself? Contact us.