CVE-2024-23741: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhyper/hyperpkg:github/hyper/hyperOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately inventory their macOS endpoints to identify installations of Hyper, particularly versions 3.4.1 and earlier. Until an official patch is released, organizations should consider the following specific mitigations: 1) Disable or restrict network access to Hyper’s remote features or any exposed services that could be exploited via RunAsNode and enableNodeClilnspectArguments settings. 2) Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious execution patterns related to Hyper processes. 3) Enforce strict network segmentation to limit the exposure of vulnerable macOS systems to untrusted networks. 4) Educate users and administrators about the risk and encourage minimizing the use of Hyper or switching to alternative terminal emulators not affected by this vulnerability. 5) Monitor security advisories from the Hyper project and macOS vendors for patches or updates and apply them promptly once available. 6) Implement robust logging and anomaly detection to identify potential exploitation attempts early. These targeted actions go beyond generic advice by focusing on the specific attack vectors and settings involved in this vulnerability.
Description
An issue in Hyper on macOS version 3.4.1 and before, allows remote attackers to execute arbitrary code via the RunAsNode and enableNodeClilnspectArguments settings.