CVE-2025-26055
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 · uneditedAn OS Command Injection vulnerability exists in the Infinxt iEdge 100 2.1.32 Troubleshoot module, specifically in the tracertVal parameter of the Tracert function.
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 confidenceA command injection vulnerability exists in the Infinxt iEdge 100 2.1.32 Troubleshoot module where the tracertVal parameter in the Tracert function is not properly sanitized before being passed to the underlying operating system, allowing an attacker to inject and execute arbitrary OS commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Confirm Infinxt iEdge 100 product identityIdentify the device model through the web interface header, system information page, or CLI command such as 'show system-info' or 'show version'Affected if The device is not an Infinxt iEdge 100
-
Verify firmware version 2.1.32Check the firmware version through the web interface (typically under Administration > System > About) or via CLI command 'show version' or 'show firmware-version'Affected if The installed version matches 2.1.32
-
Confirm Troubleshoot module accessibilityAccess the Troubleshoot module through the web interface menu or API. Look for the Tracert/Traceroute functionality within this section.Affected if The Troubleshoot module and Tracert feature are accessible to the user or API caller
-
Inspect Tracert function parameter handlingSubmit a traceroute request via the web UI or API using the tracertVal parameter with a test value containing shell metacharacters (such as semicolons or command substitution). Capture the response to observe if the injected content is executed or reflected unsanitized.Affected if The tracertVal parameter executes injected OS commands or returns unexpected command output instead of rejecting the input as invalid
The environment is affected if the device is an Infinxt iEdge 100 running version 2.1.32, the Troubleshoot module is enabled, and the tracertVal parameter in the Tracert function accepts and executes arbitrary command injection.
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.
From vendor dataImplement strict input validation and sanitization on the tracertVal parameter, preferably using a whitelist approach that only allows valid IP addresses or hostnames. If possible, use parameterized APIs instead of passing user input directly to system calls.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26055 — 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-26055 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