CVE-2026-52836

8.7

OpenDDS · OpenDDS

A memory safety vulnerability in OpenDDS allows an unauthenticated network attacker to cause a denial of service via a malformed RTPS UDP submessage.

Executive summary

An unauthenticated remote attacker can trigger a process crash in OpenDDS versions prior to 3.34.0, resulting in a denial of service for affected DDS participants.

Vulnerability

This vulnerability is an out of bounds read (CWE-125) occurring within the RTPS UDP submessage parser. An unauthenticated attacker can send a specially crafted packet that forces the application to dereference an invalid memory pointer, triggering a segmentation fault and terminating the process.

Business impact

The exploitation of this vulnerability leads to the immediate termination of the affected OpenDDS process, causing a denial of service for critical messaging infrastructure. Given the CVSS score of 8.7, this is a high severity issue that could disrupt real time data distribution systems, leading to operational downtime and potential loss of data synchronization in industrial or distributed environments.

Remediation

Immediate Action: Upgrade to OpenDDS version 3.34.0 or later to incorporate the necessary memory safety checks in the RTPS parser.

Proactive Monitoring: Monitor network traffic for malformed RTPS UDP packets and review system logs for recurring segmentation faults or unexpected process terminations.

Compensating Controls: Deploy network intrusion detection systems or firewalls configured to inspect and drop malformed RTPS traffic if immediate patching is not feasible.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

The severity of this vulnerability, combined with the lack of required authentication, necessitates immediate attention. Administrators must prioritize updating to version 3.34.0 across all affected nodes to eliminate the risk of service disruption. While no active exploitation is currently confirmed, the ease of triggerability makes patching the most effective mitigation strategy.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources