CVE-2026-120399 · Other
NO FIX YET · SEE WHAT TO DO
flightctl does a TLS handshake synchronously in the HTTP server's connection-context callback with no deadline. An unauthenticated network client that stalls the handshake stops the listener accepting new connections; existing connections are not affected. Red Hat rates it CVSS 7.5 (preliminary); no fixed version is published yet.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run flightctl with its HTTP listener reachable from the network are exposed, since the stalled handshake needs no account. The sources do not name the affected versions or the configuration needed, so check whether your flightctl deployment exposes that listener. Deployments that keep the listener off untrusted networks can skip it.
Not affected if auth-required, listener-not-exposed
Who cares dos, flightctl, self-hosted
s interim detection: periodically check the listeners Recv-Q (e.g. ss -ltn); if it is non-zero, the accept queue is stalledNo fixed version published as of 2026-11-10 (Red Hat page lists none).
A flaw was found in flightctl. A TLS handshake is performed synchronously in the HTTP server’s connection-context callback without a deadline. A network-reachable unauthenticated client can stall the handshake and prevent the affected listener from accepting new connections.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.