dbcve.org
Threadx Netx DuoApplication · Eclipse

CVE-2025-55087

HIGH · 7.5 CVSS v3.1 Published 2025-10-17
Fix available
A fix is available. Upgrade to 6.4.4.202503 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
In NextX Duo's snmp addon versions before 6.4.4, a part of the Eclipse Foundation ThreadX, an attacker could cause an out-of-bound read by a crafted SNMPv3 security parameters.

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

NextX Duo's SNMP addon (built on Eclipse Foundation ThreadX RTOS) before version 6.4.4 contains an out-of-bounds read vulnerability. Attackers can send crafted SNMPv3 security parameters to trigger the vulnerability, potentially allowing memory disclosure or denial of service.

MitigationUpgrade the NextX Duo SNMP addon to version 6.4.4 or later to obtain the patched ThreadX components.

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
Threadx Netx DuoApplication
Affected:< 6.4.4.202503

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm NetX Duo SNMP component is in use
    Search your codebase, firmware image, or dependencies for the Eclipse ThreadX NetX Duo SNMP library. Look for imports or references to nx_snmp.h, or scan binary firmware for SNMP-related strings and symbols.
    Affected if The NetX Duo SNMP addon is present in your deployed software or firmware image.
  2. Identify the ThreadX NetX Duo version
    Locate the version string for the ThreadX or NetX Duo library in your build artifacts, firmware, or documentation. Common locations: version macros in header files (NX_VERSION_ID), library file metadata, or release notes accompanying the firmware.
    Affected if The installed version is lower than 6.4.4.202503 (for example, 6.4.3.x or earlier).
  3. Verify SNMPv3 is enabled
    Review your SNMP configuration to determine if SNMPv3 protocol support is active. Check configuration files, initialization code, or runtime settings that enable SNMPv3 security parameters (AuthPass, PrivPass, or security name settings).
    Affected if SNMPv3 mode is enabled and processing of SNMPv3 security parameters is active in your deployment.
  4. Check SNMP service is exposed
    Inspect network configuration to determine if the SNMP service is listening on accessible network interfaces. Verify whether the device is configured to accept SNMP requests from non-trusted networks.
    Affected if The SNMP service is running and reachable from network segments where attackers could send crafted SNMPv3 packets.

You are affected if your deployment embeds the ThreadX NetX Duo SNMP component at a version below 6.4.4.202503 with SNMPv3 enabled and accessible to network attackers.

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 6.4.4.202503 or later
Fixed in 6.4.4.202503
Interim mitigation

Upgrade the NextX Duo SNMP addon to version 6.4.4 or later to obtain the patched ThreadX components.

Recommended fix Moderate confidence

ThreadX NetX Duo version 6.4.4.202503 or later

  1. 1. Identify all deployments of ThreadX NetX Duo SNMP addon in your environment
  2. 2. Check current version of ThreadX NetX Duo in use (versions prior to 6.4.4.202503 are affected)
  3. 3. Obtain ThreadX NetX Duo version 6.4.4.202503 or later from the Eclipse Foundation's official distribution channels
  4. 4. Review the ThreadX NetX Duo release notes for version 6.4.4 for any API or behavioral changes
  5. 5. Update the ThreadX NetX Duo library in your firmware/application to version 6.4.4.202503 or later
  6. 6. Rebuild and redeploy the affected firmware/application with the updated library
  7. 7. Verify the update was successful and test SNMP functionality

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

Fix this in Threadx Netx Duo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55087 — 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-55087 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