Skip to main content

Syself security assessment

CVE-2026-14456 in Syself Kubernetes

Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of 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-14456 affects the openssl component those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.

Not affected in 1.36 v4 Upstream severity: High Last assessed

Syself Kubernetes is not affected by CVE-2026-14456 in any of the 4 releases that ship openssl.

Reason: The vulnerable code is never executed.

Our assessment in 1.36 v4, the newest release with this finding

openssl 3.5.7
Not affected High
The vulnerable code is never executed

This flaw lets an attacker use up memory on a server that answers a newer type of network connection with this library. The system does not run any such server with this library, so the flaw is never reached.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
openssl 3.5.7Not affectedThe vulnerable code is never executed—Details

Frequently asked questions

My scanner reports CVE-2026-14456 in a Syself cluster. What should I do?

Scanners such as Trivy and Grype match package versions, so they report CVE-2026-14456 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 v4

What do the statuses mean?

Not affected
The component ships in the release, but Syself has assessed that the vulnerability cannot be exploited there. The reason column says why.
Fixed
The release ships a version of the component that carries the fix.
Affected
The vulnerability can affect the release. Upgrade to a release listed as fixed once one is available.
Under Investigation
Syself is still assessing whether the vulnerability affects the release.

Why can the severity differ from other sources?

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

References

Think this assessment is wrong, or found a vulnerability in Syself? Contact us.