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.
CVE-2025-62603
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2025-206665 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 46th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
February 3, 2026
Last Modified
June 17, 2026
Advisory Details (4)
Auto-updated Aug 6, 2026commit ced3b6f92d92 (eProsima/Fast-DDS)
Patch available: eProsima/Fast-DDS v2.6.11 (contains commit ced3b6f92d92)
https://github.com/eProsima/Fast-DDS/commit/ced3b6f92d928af1eae77d5fe889878128ad421acommit a726e6a5daba (eProsima/Fast-DDS)
Patch available: eProsima/Fast-DDS v3.3.1 (contains commit a726e6a5daba)
https://github.com/eProsima/Fast-DDS/commit/a726e6a5daba660418d1f7c05b6f203c17747d2bcommit 354218514d32 (eProsima/Fast-DDS)
Patch available: eProsima/Fast-DDS v3.4.1 (contains commit 354218514d32)
https://github.com/eProsima/Fast-DDS/commit/354218514d32beac963ff5c306f1cf159ee37c5fAffected Packages
(3 across 3 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| fastdds | 2.1.0+ds-9 ... 3.6.1+ds-1 (61 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| fastdds | 2.10.1+ds-1 ... 3.6.1+ds-1 (32 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| fastdds | 3.1.2+ds-1, 3.3.0+ds-1, 3.3.0+ds-2, 3.3.0+ds-3, 3.6.1+ds-1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 95 of 202 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-27 11:52 UTCEG score recompute
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-25 16:13 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-18 05:21 UTCEG score recompute
- 2026-10-18 02:17 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
Show 70 moreShow fewer
- 2026-10-12 16:51 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-11 20:25 UTCEG score recompute
- 2026-10-11 18:37 UTCEG score recompute
- 2026-10-11 15:12 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-09 10:58 UTCOSV refresh
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-19 18:30 UTCOSV refresh
- 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-31 21:34 UTCOSV refresh
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-14 11:25 UTCEG score recompute
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-13 03:39 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-09 16:00 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-07 22:51 UTCEG score recompute
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-08-06 04:27 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Related CVEs(same product + same CWE)
Same product
10 shownDebian:11:fastdds
Frequently asked(5)
What is CVE-2025-62603?
When was the CVE record for CVE-2025-62603 published?
Is CVE-2025-62603 actively exploited?
What is the CVSS score of CVE-2025-62603?
How do I remediate CVE-2025-62603?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-62603
Is Your Infrastructure Affected by CVE-2025-62603?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.