CVE-2026-120399

waiting for further signals

GHSA-9f6q-cw24-v4xv ↗EUVD-2026-121145 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

Red Hat Edge Manager 1

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

ETK-2026-4060, permanent identifier

cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

14h 17msince last run

25mAI analysis

timeline

0 = trigger signal

trigger signal (cve.org) +0hwaiting for further signals+2h21m

+4h

+6h

+8h

+10h

+12h

description

Red Hat Edge Manager 1 deployments using the listed flightctl API or remote-access packages are affected. An unauthenticated attacker with network access to a TLS listener can disrupt availability by causing handshake processing to block acceptance of further connections.

mitigation

Restrict access to affected TLS listeners to trusted networks and clients, and use an intermediary that applies TLS handshake time limits where possible. Monitor for vendor updates; no fixed package version is recorded.

check

exploit

automation

–

auth required

EPSS

–

agent run time

25m

cve.org record, t = 0

2026-11-10 14:08Z

Δ to public poc

–

Δ to kev

–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-11-10 14:08Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-120399

this entry in the feed

GET /api/v1/feed/CVE-2026-120399

{
  "etk_id": "ETK-2026-4060",
  "cve_id": "CVE-2026-120399",
  "display_id": "CVE-2026-120399",
  "ghsa_id": "GHSA-9f6q-cw24-v4xv",
  "euvd_id": "EUVD-2026-121145",
  "status": "published",
  "anchor_state": "anchored",
  "title": "TLS handshake denial of service in flightctl",
  "summary": "Red Hat Edge Manager 1 deployments using the listed flightctl API or remote-access packages are affected. An unauthenticated attacker with network access to a TLS listener can disrupt availability by causing handshake processing to block acceptance of further connections.",
  "mitigation": "Restrict access to affected TLS listeners to trusted networks and clients, and use an intermediary that applies TLS handshake time limits where possible. Monitor for vendor updates; no fixed package version is recorded.",
  "vendor": "Red Hat",
  "product": "Red Hat Edge Manager 1",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rhem/flightctl-api-rhel10",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rhem/flightctl-api-rhel9",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rhem/flightctl-remote-access-rhel10",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rhem/flightctl-remote-access-rhel9",
      "purl": null
    }
  ],
  "cwes": [
    1322
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.904068066666667,
  "t0_at": "2026-11-10T14:08:33.545000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T14:08:33.545000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T14:08:33.545000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-120399"
    }
  }
}

published 2026-11-10 14:46Z
last change 2026-11-11 01:54Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.