dbcve.org
Debian LinuxOperating system · Debian

CVE-2025-62799

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 2.6.11 / 3.3.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 heap buffer overflow exists in the Fast-DDS DATA_FRAG receive path. An un authenticated sender can transmit a single malformed RTPS DATA_FRAG packet where `fragmentSize` and `sampleSize` are craft ed to violate internal assumptions. Due to a 4-byte alignment step during fragment metadata initialization, the code write s past the end of the allocated payload buffer, causing immediate crash (DoS) and potentially enabling memory corruption ( RCE risk). Versions 3.4.1, 3.3.1, and 2.6.11 patch the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Fast DDS versions prior to 3.4.1, 3.3.1, and 2.6.11 contain a heap buffer overflow in the DATA_FRAG receive path. An unauthenticated attacker can send a malformed RTPS DATA_FRAG packet with crafted fragmentSize and sampleSize values that violate internal assumptions. A 4-byte alignment calculation during fragment metadata initialization causes the code to write past the end of the allocated payload buffer, enabling denial of service via crash and potential memory corruption for remote code execution.

MitigationUpgrade Fast DDS to versions 3.4.1, 3.3.1, 2.6.11 or later to patch the heap buffer overflow vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0= 12.0= 13.0
Fast DdsApplication
Affected:< 2.6.11>= 3.0.0, < 3.3.1= 3.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Fast DDS package version on Debian
    Run 'dpkg -l | grep -i fast-dds' or 'apt list --installed | grep -i fast-dds' to list installed Fast DDS packages
    Affected if The installed version is less than 2.6.11, or between 3.0.0 and 3.3.1 (exclusive), or equals 3.4.0
  2. Check Fast DDS library version
    Run 'ldconfig -p | grep fastdds' to locate the shared library, then use 'strings' or check the library filename for version info, or check /usr/lib/x86_64-linux-gnu/libfastdds* if present
    Affected if The library version cannot be determined or is older than 2.6.11, 3.3.1, or 3.4.1
  3. Verify RTPS/DDS participant is enabled
    Review application configuration files (XML profiles) or source code for DomainParticipantFactory::create_participant calls that enable RTPS communication
    Affected if The system runs any application that creates a DDS domain participant with RTPS messaging enabled (default behavior)
  4. Inspect DATA_FRAG receive configuration
    Check if the environment allows external RTPS connections by reviewing network bindings, firewall rules, or participant configuration for RTPS transport (default UDP or TCP ports 7400-7407)
    Affected if The Fast DDS participant is accessible over the network on RTPS ports, allowing external entities to send DATA_FRAG packets

A system is affected if it runs any version of Fast DDS older than 2.6.11, 3.3.1, or 3.4.1 with RTPS communication enabled and exposed to network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.11 / 3.3.1 or later
Fixed in 2.6.113.3.1
Vendor patch github.com →
Interim mitigation

Upgrade Fast DDS to versions 3.4.1, 3.3.1, 2.6.11 or later to patch the heap buffer overflow vulnerability.

Recommended fix High confidence

Fast DDS 2.6.11 (for 2.x users), 3.3.1 (for 3.0.0-3.3.x users), or 3.4.1 (for 3.4.0 users)

  1. 1. Identify the currently installed Fast DDS version by checking project dependencies or library version
  2. 2. For Fast DDS 2.x users: Upgrade to version 2.6.11 or later
  3. 3. For Fast DDS 3.x users (3.0.0 to 3.3.x): Upgrade to version 3.3.1 or later
  4. 4. For Fast DDS 3.4.0 users: Upgrade to version 3.4.1 or later
  5. 5. Rebuild and recompile any dependent projects that link against Fast DDS
  6. 6. Test the application to verify the upgrade does not introduce regressions
  7. 7. For Debian systems: Monitor for package updates via security-tracker.debian.org and apply system packages once available
Caveat Upgrade within same major version should be compatible; test thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62799 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data