Skip to main content
VulnerabilityPublished

CVE-2026-26011: ros-navigation navigation2 · Out-of-bounds Write

Affects ros-navigation navigation2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ros-navigationnavigation2Affected
  • <=1.3.11
Fixed in–

AI-suggested

To mitigate CVE-2026-26011, organizations should immediately upgrade navigation2 to a patched version once available, as no patches were linked at the time of disclosure. Until patches are released, implement strict network segmentation and access controls to restrict ROS 2 DDS domain access only to trusted and authenticated nodes, minimizing exposure to unauthenticated attackers. Employ ROS 2 security features such as DDS Security plugins to enforce authentication, encryption, and access control policies. Monitor ROS 2 topics, especially /initialpose, for anomalous or malformed messages with extreme covariance values using custom validation or intrusion detection systems tailored for ROS 2 message traffic. Consider deploying runtime memory protection tools and heap integrity checkers to detect and prevent heap corruption attempts. Conduct thorough code audits and fuzz testing on navigation2 components to identify and remediate similar vulnerabilities proactively. Finally, establish incident response plans specific to robotic system compromises to quickly isolate and recover affected systems.

Description

navigation2 is a ROS 2 Navigation Framework and System. In 1.3.11 and earlier, a critical heap out-of-bounds write vulnerability exists in Nav2 AMCL's particle filter clustering logic. By publishing a single crafted geometry_msgs/PoseWithCovarianceStamped message with extreme covariance values to the /initialpose topic, an unauthenticated attacker on the same ROS 2 DDS domain can trigger a negative index write (set->clusters[-1]) into heap memory preceding the allocated buffer. In Release builds, the sole boundary check (assert) is compiled out, leaving zero runtime protection. This primitive allows controlled corruption of the heap chunk metadata(at least the size of the heap chunk where the set->clusters is in is controllable by the attacker), potentially leading to further exploitation. At minimum, it provides a reliable single-packet denial of service that kills localization and halts all navigation.

References

Community reviews

Loading reviews…