Skip to main content
CVE-2024-41645VulnerabilityPublished Updated

CVE-2024-41645: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 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 52% 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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-41645, organizations should first monitor official Open Robotics channels for patches or updates addressing the insecure permissions in the nav2__amcl module and apply them immediately upon release. In the absence of patches, restrict network access to ROS2 navigation2 components by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks. Employ application-level access controls and sandboxing to constrain the execution environment of navigation2 processes. Conduct thorough permission audits on ROS2 components to ensure least privilege principles are enforced, removing unnecessary write or execute permissions on scripts and configuration files. Additionally, implement runtime monitoring and anomaly detection to identify unusual script executions or process behaviors indicative of exploitation attempts. For environments where physical safety is critical, consider deploying additional safety interlocks or manual overrides to prevent robotic malfunctions triggered by compromised navigation modules. Finally, maintain up-to-date backups and incident response plans tailored to robotic system compromises.

Description

Insecure Permissions vulnerability in Open Robotics Robotic Operating System 2 ROS2 navigation2 v.humble allows an attacker to execute arbitrary code via a crafted script to the nav2__amcl.

References

Community reviews

Loading reviews…