CVE-2026-22590: Fast-DDS Discovery Server: Out-of-Bounds Read & Heap Memory Disclosure via DATA_FRAG sampleSize / fragmentsInSubmessage
eprosima Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group). Versions prior to 2.6.12, 2.14.6, 3.2.4, 3.3.1, and 3.4.2 have a remotely triggerable Out-of-Bounds Read while processing RTPS DATAFRAG submessages. An attacker can craft a DATAFRAG with a large sampleSize but a small actual payload, and set fragmentsInSubmessage such that the receiver treats the packet as the LAST fragment. In this LAST-fragment path, Fast-DDS computes incominglength based on sampleSize and calls memcpy() without validating incomingdata.length >= incominglength. As a result, CacheChanget::addfragments() reads past the received UDP datagram buffer and into adjacent heap memory, copying those bytes into the reassembly buffer. In a Discovery Server deployment, the resulting CacheChanget can be relayed to other participants, meaning that a newly joining participant may receive leaked heap memory (e.g., pointer values that could aid ASLR bypass). Versions 2.6.12, 2.14.6, 3.2.4, 3.3.1, and 3.4.2 fix the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
eprosima Fast DDSto a version that resolves this vulnerability.Fixed in 2.6.12 - Upgrade
Upgrade
eprosima Fast DDSto a version that resolves this vulnerability.Fixed in 2.14.6 - Upgrade
Upgrade
eprosima Fast DDSto a version that resolves this vulnerability.Fixed in 3.2.4 - Upgrade
Upgrade
eprosima Fast DDSto a version that resolves this vulnerability.Fixed in 3.3.1 - Upgrade
Upgrade
eprosima Fast DDSto a version that resolves this vulnerability.Fixed in 3.4.2
Event History
Frequently Asked Questions
Which deployments are most exposed to heap-memory disclosure?
Discovery Server deployments are specifically exposed because the malformed DATA_FRAG can produce a CacheChange_t that the server relays to other participants. A newly joining participant may therefore receive heap bytes read from the server process.
What does an attacker need to exploit this issue?
The attacker needs to send a crafted RTPS DATA_FRAG submessage to a vulnerable Fast DDS receiver. The exploit uses a large sampleSize with a small actual payload and fragmentsInSubmessage values that make the receiver take the LAST-fragment path; no privileges or user interaction are required.
Are fixed versions available?
Yes. The issue is fixed in versions 2.6.12, 2.14.6, 3.2.4, 3.3.1, and 3.4.2; versions earlier than those releases in their respective branches are affected.