CVE-2026-134044 in ROS 2info

Summary

by MITRE • 11/20/2026

Open Robotics ROS 2 sros2 load_policy XML External Entity Processing Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Open Robotics ROS 2. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of policy XML files. Due to the improper restriction of XML External Entity (XXE) references, a crafted document specifying a URI causes the XML parser to access the URI and embed the contents back into the XML document for further processing. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current user. Was ZDI-CAN-32121.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified as CVE-2024-XXXX, associated with Zero Day Initiative identifier ZDI-CAN-32121, represents a critical security flaw within the ROS 2 sros2 component of Open Robotics' Robot Operating System framework. This issue stems from an improper restriction of XML External Entity references during the parsing of policy configuration files. In standard XML processing, external entities allow documents to reference resources located outside the primary document structure. When parsers are not strictly configured to disable or sanitize these references, they become susceptible to XML External Entity attacks. The sros2 component, responsible for managing security policies and authentication mechanisms in ROS 2 environments, relies heavily on XML-based policy files to define access controls and cryptographic parameters. The failure to properly validate or restrict the sources of these entities creates a significant attack surface that can be exploited by malicious actors targeting systems running vulnerable versions of this software.

The technical mechanism behind this vulnerability involves the manipulation of URI references within crafted XML documents. When an attacker provides a specially constructed policy file containing external entity definitions pointing to arbitrary Uniform Resource Identifiers, the underlying XML parser processes these directives without adequate safeguards. Instead of ignoring or rejecting such requests, the parser resolves the URIs and embeds their contents directly back into the document structure for further processing. This behavior effectively turns the application into an active proxy that fetches remote resources and incorporates them into its internal state. In a typical scenario requiring user interaction, this exploitation vector might be triggered when a developer or system administrator opens a maliciously crafted policy file in an integrated development environment or configuration tool associated with ROS 2. The act of opening such a file initiates the parsing routine that inadvertently retrieves data from external sources controlled by the attacker.

The operational impact of this vulnerability is primarily characterized as an information disclosure risk, although it carries potential for more severe consequences depending on the surrounding system architecture and available auxiliary vulnerabilities. By forcing the application to fetch content from arbitrary URIs, attackers can potentially exfiltrate sensitive configuration details, internal network topology data, or other confidential information stored in accessible locations reachable by the target machine. Furthermore, because ROS 2 often operates with elevated privileges to manage hardware interfaces and real-time control systems, any compromise of the policy loading mechanism could lead to broader system instability or unauthorized access. While the primary classification is information disclosure, the ability to inject arbitrary content into the processing pipeline means that this flaw can serve as a stepping stone for more complex attacks if combined with other weaknesses in the application logic or underlying operating system protections.

From a threat modeling perspective, this vulnerability aligns closely with CWE-611, which describes Improper Restriction of XML External Entity Reference. This classification highlights the failure to implement proper input validation and sanitization procedures when handling structured data formats that support external references. Additionally, the exploitation technique relates to ATT&CK tactic T1502, specifically sub-technique T1502.001 regarding Use of Resource Development Kits or Libraries with Known Vulnerabilities if the parser library itself is outdated, but more accurately maps to techniques involving data exfiltration via application logic flaws. The requirement for user interaction places this vulnerability in a lower initial severity tier compared to remote code execution vectors that require no human intervention, yet its presence in security-critical infrastructure software like ROS 2 elevates the risk profile significantly due to the potential lateral movement and privilege escalation opportunities it presents within robotic systems networks.

Mitigation strategies must focus on hardening the XML parsing configuration used by sros2. The most effective remediation involves disabling external entity processing entirely if such functionality is not strictly required for legitimate policy operations. This can typically be achieved by configuring the underlying XML parser to reject DTDs and external entities, ensuring that only local or explicitly whitelisted resources are permitted during policy loading. Organizations should also implement strict input validation checks on all incoming configuration files before they reach the parsing engine. Regular security audits of ROS 2 deployments are recommended to identify instances where default configurations might expose this weakness. Updating to patched versions of Open Robotics ROS 2 that address ZDI-CAN-32121 is essential for maintaining the integrity and confidentiality of robotic systems relying on sros2 for secure communication and access control management.

Responsible

Zdi

Reservation

11/20/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00290

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!