Skip to main content
VulnerabilityPublished Updated

CVE-2024-38921: Use After Free

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-38921, organizations should immediately implement network segmentation and restrict access to ROS2 nodes, especially the nav2_amcl process and its dynamic parameter interfaces. Employ strict firewall rules and access controls to limit who can send parameter change requests. Monitor network traffic for anomalous or unauthorized parameter modification attempts. Until official patches are released, consider disabling or isolating the AMCL node if feasible, or deploying additional runtime protections such as memory safety tools or intrusion detection systems tailored for ROS2 environments. Conduct thorough security assessments of robotic systems and update incident response plans to include potential exploitation scenarios. Engage with the ROS2 community and vendors for timely updates and patches. Additionally, implement robust authentication and authorization mechanisms for dynamic parameter changes to prevent unauthorized access. Regularly audit and update robotic software dependencies to minimize exposure to known vulnerabilities.

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_rand ` .

References

Community reviews

Loading reviews…