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.
Published: 2026-11-10
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

Vendor Workaround

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.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 10 Nov 2026 14:15:00 +0000

Type Values Removed Values Added
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.
Title Flightctl-api: flightctl-remote-access: flightctl: unbounded tls handshake in conncontext can block accepting connections
First Time appeared Redhat
Redhat edge Manager
Weaknesses CWE-1322
CPEs cpe:/a:redhat:edge_manager:1
Vendors & Products Redhat
Redhat edge Manager
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

Redhat Edge Manager
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-11-10T14:08:33.545Z

Reserved: 2026-11-02T09:41:54.480Z

Link: CVE-2026-120399

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-10T14:17:14.300

Modified: 2026-11-10T14:17:14.417

Link: CVE-2026-120399

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses
  • CWE-1322

    Use of Blocking Code in Single-threaded, Non-blocking Context