CVE-2026-52836 OpenDDS CVE debrief

Who should care

Defenders responsible for OpenDDS deployments should assess exposure and prioritize updates to prevent potential crashes caused by malformed RTPS UDP submessages. This includes reviewing OpenDDS participant configurations, monitoring OpenDDS logs for potential crashes or errors, and verifying OpenDDS version and configuration.

Why it matters

Defenders should prioritize updating OpenDDS to version 3.34.0 or later to prevent potential crashes caused by malformed RTPS UDP submessages. This vulnerability allows a network attacker to crash a reachable OpenDDS participant, potentially impacting DDS entities hosted by that participant.

• Potential crashes of OpenDDS participants
• Denial of Service (DoS) due to crashes
• Need for verification of OpenDDS version and configuration
• Potential impact on DDS entities hosted by the participant

Technical summary

The vulnerability is caused by the lack of validation of the read pointer in RtpsUdpReceiveStrategy::handle_input() and RtpsSampleHeader::init(). This allows a network attacker to crash a reachable OpenDDS participant by sending a malformed RTPS UDP submessage. The resulting SIGSEGV occurs in the receive thread, terminates the DDS process, and destroys the DDS entities hosted by that participant. The issue is fixed in version 3.34.0 and later, which validates the read pointer and prevents such crashes. Defenders should prioritize updating OpenDDS to version 3.34.0 or later to prevent potential crashes caused by malformed RTPS UDP submessages.

Defensive priority

Defenders should prioritize updating OpenDDS to version 3.34.0 or later to prevent potential crashes caused by malformed RTPS UDP submessages.

Recommended defensive actions

• Update OpenDDS to version 3.34.0 or later
• Verify OpenDDS participant configurations to prevent exposure to untrusted networks
• Monitor OpenDDS logs for potential crashes or errors
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the lack of validation of the read pointer in RtpsUdpReceiveStrategy::handle_input() and RtpsSampleHeader::init(). The parser can then call dds/DCPS/transport/rtps_udp/RtpsSampleHeader.cpp in RtpsSampleHeader::init(), which dereferences the invalid read pointer without first validating it against wr_ptr() or ensuring that a complete submessage header remains. No authentication, prior protocol state, or victim interaction is required.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.