VulnerabilityPublished 3 Feb 2026

CVE-2025-62603: eProsima Fast-DDS · Out-of-bounds Read

Affects eProsima Fast-DDSSource CVE Database V5

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, 12:29 UTC

CVSS 4.0 base score

1.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

Affected software

Product	Affected	Fixed in
eProsimaFast-DDS	Affected >=3.4.0 <3.4.1	Fixed in 3.4.1
eProsimaFast-DDS	Affected >=3.0.0 <3.3.1	Fixed in 3.3.1
eProsimaFast-DDS	Affected <2.6.11	Fixed in 2.6.11
GitHubeprosima/Fast-DDS`pkg:github/eprosima/Fast-DDS`Other threats	Affected =0 =3.0.0 =3.4.0	Fixed in–
GitHubFast-DDS`pkg:github/Fast-DDS`Other threats	Affected >=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

The primary mitigation is to upgrade eProsima Fast-DDS to versions 3.4.1, 3.3.1, or 2.6.11 or later, where the vulnerability is patched. Organizations should audit their environments to identify Fast-DDS deployments and ensure timely patching. Network-level controls should be implemented to restrict DDS traffic to trusted sources only, employing firewall rules or network segmentation to isolate DDS communication channels. Deploying intrusion detection systems (IDS) or anomaly detection tailored to DDS traffic patterns can help identify malformed or suspicious messages. Additionally, applying rate limiting on DDS security messages may reduce the risk of resource exhaustion. Developers and integrators should review their use of ParticipantGenericMessage parsing to ensure minimal header checks are performed before full deserialization, reducing exposure to malformed inputs. Regular security assessments and penetration testing focusing on DDS implementations can help detect similar vulnerabilities proactively.

Description

Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group ). ParticipantGenericMessage is the DDS Security control-message container that carries not only the handshake but also on going security-control traffic after the handshake, such as crypto-token exchange, rekeying, re-authentication, and token delivery for newly appearing endpoints. On receive, the CDR parser is invoked first and deserializes the `message_data` (i .e., the `DataHolderSeq`) via the `readParticipantGenericMessage → readDataHolderSeq` path. The `DataHolderSeq` is parsed sequentially: a sequence count (`uint32`), and for each DataHolder the `class_id` string (e.g. `DDS:Auth:PKI-DH:1.0+Req`), string properties (a sequence of key/value pairs), and binary properties (a name plus an octet-vector). The parser operat es at a stateless level and does not know higher-layer state (for example, whether the handshake has already completed), s o it fully unfolds the structure before distinguishing legitimate from malformed traffic. Because RTPS permits duplicates, delays, and retransmissions, a receiver must perform at least minimal structural parsing to check identity and sequence n umbers before discarding or processing a message; the current implementation, however, does not "peek" only at a minimal header and instead parses the entire `DataHolderSeq`. As a result, prior to versions 3.4.1, 3.3.1, and 2.6.11, this parsi ng behavior can trigger an out-of-memory condition and remotely terminate the process. Versions 3.4.1, 3.3.1, and 2.6.11 p atch the issue.

Impact

For European organizations, especially those in sectors relying on real-time data distribution such as industrial automation, automotive, aerospace, and critical infrastructure, this vulnerability poses a risk of denial-of-service through remote process termination. Disruption of Fast-DDS services could impact operational continuity, safety systems, and real-time control processes. Although the vulnerability does not directly compromise confidentiality or integrity, availability impacts could cascade into operational delays or failures. Given the low CVSS score, the immediate risk is limited, but targeted attacks exploiting this flaw could affect high-value systems. The lack of authentication requirements means attackers can attempt exploitation from the network, increasing exposure if DDS traffic is not properly segmented or filtered. European organizations using Fast-DDS in IoT, robotics, or distributed control systems should be particularly vigilant.

Summary

The vulnerability CVE-2025-62603 resides in eProsima Fast-DDS, a widely used C++ implementation of the OMG DDS standard for real-time data distribution. Fast-DDS uses ParticipantGenericMessage containers to carry DDS Security control messages, including handshake and ongoing security traffic such as crypto-token exchanges and re-authentication. The vulnerability arises during the deserialization process of the message_data field, specifically within the DataHolderSeq sequence. The parser fully unfolds the entire DataHolderSeq structure without performing minimal header checks to validate message legitimacy before parsing. This behavior is problematic because RTPS (Real-Time Publish-Subscribe) protocol allows duplicates, delays, and retransmissions, necessitating at least minimal structural parsing before processing. However, the current implementation parses the entire sequence, which can be malformed or crafted maliciously to cause an out-of-bounds read. This can lead to an out-of-memory condition and remote process termination, effectively causing a denial-of-service (DoS). The vulnerability affects Fast-DDS versions prior to 3.4.1, 3.3.1, and 2.6.11, which have patched this issue. Exploitation requires no authentication or user interaction and can be triggered remotely by sending specially crafted DDS security messages. The CVSS 4.0 score is 1.7, indicating low severity primarily due to limited impact on confidentiality, integrity, and the requirement for specific protocol knowledge to exploit. No known exploits are reported in the wild as of now.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Feb 2026, 20:01 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats