CVE-2024-26369: Fast-DDS · Uncontrolled Resource Consumption
Affects Fast-DDSSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 2.12.0 : patch Fast-DDS soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.12.0, 2.11.0, 2.7.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade eprosima/Fast-DDS to 2.12.0, 2.11.0 or 2.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubeprosima/Fast-DDSpkg:github/eprosima/Fast-DDSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Restrict network access to FastDDS endpoints by implementing strict firewall rules and network segmentation to limit exposure to untrusted sources.
- Monitor FastDDS processes for abnormal terminations and implement automated restart mechanisms to minimize downtime.
- Employ application-layer filtering or validation to detect and block malformed or suspicious DataWriter messages that could trigger the SIGABRT.
- Engage with the FastDDS community or vendor for updates and patches addressing this vulnerability as they become available.
- Conduct thorough testing of FastDDS deployments under load and malformed input conditions to identify and mitigate potential crash triggers.
- Where possible, isolate critical FastDDS components in hardened environments with minimal external exposure.
- Implement logging and alerting for unusual network activity or process crashes to enable rapid incident response.
- Consider alternative DDS implementations or versions not affected by this vulnerability if immediate patching is not feasible.
Description
An issue in the HistoryQosPolicy component of FastDDS v2.12.x, v2.11.x, v2.10.x, and v2.6.x leads to a SIGABRT (signal abort) upon receiving DataWriter's data.