CVE-2024-37861: Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% 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 5 Dec 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
AI-suggested
Until an official patch is released, organizations should implement several specific mitigation strategies. First, restrict network access to the nav2_amcl process by enforcing strict firewall rules and network segmentation to limit exposure to untrusted sources. Second, implement input validation and sanitization controls on any .yaml files accepted by the system, ensuring only trusted and verified configuration files are processed. Third, monitor network traffic and system logs for unusual activity or malformed .yaml file submissions that could indicate exploitation attempts. Fourth, consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect buffer overflow patterns or anomalous behavior in ROS2 components. Finally, maintain an active vulnerability management program to apply patches promptly once they become available from Open Robotics. Organizations should also review and update incident response plans to address potential exploitation scenarios involving robotic systems.
Description
Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a buffer overflow via the nav2_amcl process. This vulnerability is triggered via sending a crafted .yaml file.