CVE-2026-120399: Red Hat Edge Manager 1 · Use of Blocking Code in Single-threaded, Non-blocking Context
Affects Red Hat Edge Manager 1Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 10 Nov 2026, 14:34 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Edge Manager 1rhem/flightctl-api-rhel10 | Affected– | Fixed in– |
| Red Hat Edge Manager 1rhem/flightctl-api-rhel9 | Affected– | Fixed in– |
| Red Hat Edge Manager 1rhem/flightctl-remote-access-rhel10 | Affected– | Fixed in– |
| Red Hat Edge Manager 1rhem/flightctl-remote-access-rhel9 | Affected– | Fixed in– |
AI-suggested
Red Hat advises recovering affected services by restarting the server and blocking the malicious client at the network level. As a temporary workaround, scheduling recurrent checks on the listener's Recv-Q to terminate idle connections that have received almost no data can help mitigate the issue.
Description
CVE-2026-120399 is a vulnerability in Red Hat Edge Manager 1's flightctl component where a TLS handshake is performed synchronously without a deadline in the HTTP server's connection-context callback. This allows a network-reachable unauthenticated client to stall the handshake process, causing the affected listener to stop accepting new connections. Existing connections remain unaffected. The issue results in a denial of service (DoS) by resource exhaustion.