Cyber Resilience

CVE-2025-64438

DoS in Eprosima Fast Dds ≤ 2.6.11

Published
03 February 2026
Modified
18 February 2026
Patch / advisory
CVSS Score v4 1.7
Click a component to see what it means
Raw vectorCVSS: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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0054 43th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2025-64438 is a low-severity Infinite Loop (CWE-835) vulnerability in Eprosima Fast Dds. Its CVSS base score is 1.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-64438 is a remotely triggerable out-of-memory (OOM) denial-of-service vulnerability in Fast DDS, a C++ implementation of the OMG Data Distribution Service (DDS) standard. It affects versions prior to 3.4.1, 3.3.1, and 2.6.11, specifically when processing RTPS GAP submessages under RELIABLE QoS. An attacker can send a small GAP packet with a huge gap range (gapList.base - gapStart), causing StatefulReader::processGapMsg() to enter an unbounded loop that inserts millions of sequence numbers into WriterProxy::changes_received_ (a std::set), resulting in multi-GB heap growth and process termination. The issue is classified as CWE-835 with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Any attacker with network reachability to a vulnerable DDS reader on the relevant domain can exploit this, as no authentication is required. Exploitation triggers rapid memory exhaustion—up to approximately 64 GB observed in non-ASan environments without resource limits—leading to process crash and denial of service. The attack relies solely on crafting and sending malformed RTPS GAP submessages, making it straightforward for remote unauthenticated actors.

Patches addressing this vulnerability are available in Fast DDS versions 3.4.1, 3.3.1, and 2.6.11, with specific fixes implemented in GitHub commits 0b0cb308eaeeb2175694aa0a0a723106824ce9a7, 71da01b4aea4d937558984f2cf0089f5ba3c871f, and 8ca016134dac20b6e30e42b7b73466ef7cdbc213. Security practitioners should upgrade to these versions and review the Debian security tracker at https://security-tracker.debian.org/tracker/CVE-2025-64438 for distribution-specific guidance.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-63829Same product: Eprosima Fast Dds
CVE-2023-42459Same product: Eprosima Fast Dds
CVE-2024-28231Same product: Eprosima Fast Dds
CVE-2025-24807Same product: Eprosima Fast Dds
CVE-2024-30259Same product: Eprosima Fast Dds
CVE-2023-50257Same product: Eprosima Fast Dds
CVE-2024-30916Same product: Eprosima Fast Dds
CVE-2024-30258Same product: Eprosima Fast Dds
CVE-2023-50716Same product: Eprosima Fast Dds
CVE-2024-30917Same product: Eprosima Fast Dds

Affected Assets

eprosima
fast dds
3.4.0 · ≤ 2.6.11 · 3.0.0 — 3.3.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.

Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.

Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can uncover infinite-loop conditions before release.

prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

prevents

Secure coding standards directly address loop termination and prevent infinite loops.

none

Secure architecture principles encourage designs that avoid unreachable exit conditions.

none

Change management can require review of loop logic when code is modified.

References