CVE-2024-38920: Use After Free
Source CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% 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:N/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
To mitigate CVE-2024-38920, organizations should immediately restrict network access to the nav2_amcl service, ideally isolating robotic systems from untrusted networks and applying strict firewall rules to limit parameter change requests to trusted sources only. Implement network segmentation to separate robotic control networks from general IT infrastructure. Monitor network traffic for unusual or unauthorized dynamic parameter modification attempts targeting `/amcl max_beams`. Apply any available patches or updates from the ROS2 or Nav2 maintainers as soon as they are released. If patches are not yet available, consider disabling or limiting the dynamic parameter feature if feasible, or deploying runtime protections such as memory safety tools and intrusion detection systems tailored for robotic environments. Conduct thorough security assessments of robotic deployments to identify and remediate similar vulnerabilities. Finally, maintain up-to-date incident response plans specific to robotic system compromises.
Description
Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggerd via remotely sending a request for change the value of dynamic-parameter`/amcl max_beams` .