CVE-2026-120399

Flightctl-api: flightctl-remote-access: flightctl: unbounded tls handshake in conncontext can block accepting connections

  • High 7.5

Description

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.

Key facts

Published
10 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.343% likely to be exploited in the next 30 days, higher than 28.295% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

What to do

  • The services can be recovered by restarting the server and blocking the malicious device at network level. As a temporary workaround, you can schedule a recurrent check on the listener's Recv-Q; when the queue is non-zero, this terminates idle connections that have received almost no data.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Edge Manager 1
  • Default status: affected
Red HatRed Hat Edge Manager 1
  • Default status: affected
Red HatRed Hat Edge Manager 1
  • Default status: affected
Red HatRed Hat Edge Manager 1
  • Default status: affected

Timeline

  1. 2 Nov 2026 Reported to Red Hat.
  2. 10 Nov 2026 Made public.
  3. 10 Nov 2026 Published

Weakness

References