Skip to main content
CVE-2025-64438VulnerabilityPublished

CVE-2025-64438: eProsima Fast-DDS · Infinite Loop

Affects eProsima Fast-DDSSource CVE Database V5

0

Not known to be exploited · CVSS 1.7 Low · fixed in 3.4.1 : update eProsima Fast-DDS when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
1.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.4.1, 3.3.1, 2.6.11
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Upgrade eProsima Fast-DDS to 3.4.1, 3.3.1 or 2.6.11.

Affected software

ProductAffectedFixed in
eProsimaFast-DDSAffected
  • >=3.4.0 <3.4.1
  • >=3.0.0 <3.3.1
  • <2.6.11
Fixed in
  • 3.4.1
  • 3.3.1
  • 2.6.11
GitHubeprosima/Fast-DDSpkg:github/eprosima/Fast-DDSOther threatsAffected
  • =0
  • =3.0.0
  • =3.4.0
Fixed in–
GitHubFast-DDSpkg:github/Fast-DDSOther threatsAffected
  • >=3.4.0 <3.4.1
  • >=3.0.0 <3.3.1
  • <2.6.11
Fixed in
  • 3.4.1
  • 3.3.1
  • 2.6.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade eProsima Fast-DDS to versions 3.4.1, 3.3.1, or 2.6.11 or later where the vulnerability is patched. 2. Implement network segmentation and restrict access to DDS domain readers to trusted hosts only, minimizing exposure to untrusted networks. 3. Employ network-level filtering to block malformed or suspicious RTPS GAP submessages, if feasible. 4. Monitor memory usage of Fast-DDS processes and set resource limits to prevent excessive memory consumption. 5. Use intrusion detection systems capable of recognizing anomalous DDS traffic patterns. 6. Conduct regular security assessments of DDS deployments, including penetration testing focused on protocol fuzzing. 7. Where possible, enable authentication and encryption features of DDS to reduce unauthorized access risk. 8. Maintain up-to-date incident response plans for denial-of-service scenarios affecting real-time communication middleware.

Description

Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group ). Prior to versions 3.4.1, 3.3.1, and 2.6.11, a remotely triggerable Out-of-Memory (OOM) denial-of-service exists in Fast -DDS when processing RTPS GAP submessages under RELIABLE QoS. By sending a tiny GAP packet with a huge gap range (`gapList .base - gapStart`), an attacker drives `StatefulReader::processGapMsg()` into an unbounded loop that inserts millions of s equence numbers into `WriterProxy::changes_received_` (`std::set`), causing multi-GB heap growth and process termination. No authentication is required beyond network reachability to the reader on the DDS domain. In environments without an RSS limit (non-ASan / unlimited), memory consumption was observed to rise to ~64 GB. Versions 3.4.1, 3.3.1, and 2.6.11 patch t he issue.

References

Community reviews

Loading reviews…