dbcve.org
Insightconnect TracerouteApplication · Rapid7

CVE-2026-8666

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 1.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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
OS Command Injection vulnerability in the traceroute action of Rapid7 InsightConnect Traceroute Plugin on Linux allows remote attackers to execute arbitrary OS commands via the host, port, max_ttl, count, or time_out request parameters due to insufficient input validation when constructing shell commands.

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

The Rapid7 InsightConnect Traceroute Plugin for Linux suffers from OS command injection due to unsafe construction of shell commands using user-supplied input. The host, port, max_ttl, count, and time_out parameters are passed directly to shell execution without sanitization, allowing attackers to inject arbitrary OS commands.

MitigationImplement strict input validation and use parameterized command execution instead of shell string interpolation to prevent command injection.

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
Insightconnect TracerouteApplication
Affected:< 1.0.3

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. Locate the InsightConnect Traceroute plugin installation
    Search for plugin files named 'traceroute' or 'Traceroute' within the InsightConnect installation directory, typically found under the plugins or extensions folder
    Affected if The plugin files are present on the system
  2. Determine the installed plugin version
    Check the plugin manifest, metadata file, or version info associated with the Traceroute plugin (often in a .json, .xml, or VERSION file within the plugin directory)
    Affected if The version number is found to be less than 1.0.3
  3. Verify the plugin is enabled in InsightConnect
    Check the InsightConnect platform configuration or plugin management interface to confirm the Traceroute plugin status shows as enabled or active
    Affected if The plugin is enabled and available for workflow or API use
  4. Confirm the plugin exposes the vulnerable parameters
    Review the plugin's exposed actions, API endpoints, or workflow triggers to verify the host, port, max_ttl, count, and time_out parameters are exposed for user input
    Affected if One or more of these parameters accept user-supplied input and are used in traceroute execution

The environment is affected if the Traceroute plugin version is below 1.0.3, the plugin is enabled, and the vulnerable parameters can receive untrusted input that reaches shell command construction.

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

Implement strict input validation and use parameterized command execution instead of shell string interpolation to prevent command injection.

Recommended fix Moderate confidence

InsightConnect Traceroute Plugin version 1.0.3

  1. Upgrade the InsightConnect Traceroute Plugin to version 1.0.3 or later via the Rapid7 Extension Library at extensions.rapid7.com
  2. After upgrading, verify the plugin version in the InsightConnect plugin management interface
  3. Test the traceroute functionality to ensure it still works correctly with the updated plugin

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

Fix this in Insightconnect Traceroute Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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