CVE-2024-38926: 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 47% 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 6 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-38926, organizations should implement the following specific measures: 1) Immediately restrict network access to the nav2_amcl service by using firewalls, network segmentation, or VPNs to limit exposure only to trusted entities. 2) Monitor and log all dynamic parameter change requests, especially those targeting `/amcl z_short`, to detect suspicious or unauthorized attempts. 3) Apply patches or updates from Open Robotics as soon as they become available; maintain close communication with ROS2 maintainers for timely security releases. 4) Employ runtime protections such as memory safety tools (e.g., AddressSanitizer) during development and testing to detect use-after-free conditions. 5) Conduct thorough code reviews and static analysis on custom ROS2 components that interact with dynamic parameters to identify similar vulnerabilities. 6) Develop incident response plans specific to robotic system compromises, including safe shutdown procedures to mitigate physical risks. These targeted actions go beyond generic advice by focusing on the unique aspects of ROS2 and robotic operational environments.
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 triggered via remotely sending a request for change the value of dynamic-parameter `/amcl z_short`.