CVE-2025-55094
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 · uneditedIn NetX Duo before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_icmpv6_validate_options() when handling a packet with ICMP6 options.
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 confidenceNetX Duo before 6.4.4 contains an out-of-bounds read vulnerability in the _nx_icmpv6_validate_options() function when processing ICMPv6 packets with options. The function fails to properly validate buffer boundaries before reading option data, potentially allowing an attacker to read memory beyond the allocated packet buffer.
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< 6.4.4.202503CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetX Duo versionLocate the NetX Duo library or header files (commonly nx_api.h or version.h) and read the version definition. The version is typically defined as NX_DUO_VERSION_MAJOR, NX_DUO_VERSION_MINOR, or in a version string. Compare the version number to 6.4.4.202503.Affected if The installed version is less than 6.4.4.202503.
-
Verify ICMPv6 is enabledCheck the NetX Duo configuration header (usually nx_user.h or a build-config file) for the definition NX_ENABLE_IPV6_MULTICAST or NX_ENABLE_ICMPV6. Confirm these are set to a non-zero value indicating ICMPv6 support is compiled in.Affected if ICMPv6 support (NX_ENABLE_ICMPV6) is defined and enabled in the build configuration.
-
Confirm ICMPv6 packet processing is usedReview application code to determine if the NetX Duo ICMPv6 API functions are called, such as nx_icmpv6_ra_flag_set, nx_icmpv6_router_solicitation_send, or if IPv6 interface initialization (nx_ip_v6_*. functions) is performed.Affected if The application initializes IPv6 interfaces or uses ICMPv6 services, making the vulnerable code path reachable.
You are affected if your NetX Duo version is below 6.4.4.202503 AND ICMPv6 support is enabled and used in your deployment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.4.4.202503
Upgrade NetX Duo to version 6.4.4 or later to obtain the patch for this vulnerability.
NetX Duo 6.4.4.202503 or later
- 1. Identify all deployments of ThreadX NetX Duo in your codebase or embedded systems
- 2. Verify the current version of NetX Duo being used (check your build system, dependencies, or firmware)
- 3. Obtain NetX Duo version 6.4.4.202503 or later from the Eclipse Foundation (official source or your vendor)
- 4. Update the NetX Duo library dependency in your build configuration or replace the binary in your firmware
- 5. Rebuild and test your application to ensure the upgrade does not break existing functionality
- 6. Deploy the updated firmware/software to all affected devices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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