dbcve.org
Insightconnect PingApplication · Rapid7

CVE-2026-8660

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 1.0.4 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 ping action of Rapid7 InsightConnect Ping Plugin on Linux allows remote attackers to execute arbitrary OS commands via the host parameter 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 Ping Plugin on Linux contains an OS command injection vulnerability in its ping action. The host parameter is not properly validated or sanitized before being incorporated into a shell command, allowing an attacker to inject arbitrary OS commands. A remote attacker can craft malicious input in the host parameter to break out of the intended ping command and execute arbitrary commands on the underlying Linux system.

MitigationImplement strict input validation and use parameterized command execution (e.g., passing arguments safely rather than shell string concatenation) to ensure the host parameter cannot contain shell metacharacters or command separators.

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 PingApplication
Affected:< 1.0.4

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. Confirm InsightConnect is installed
    Locate the Rapid7 InsightConnect installation directory. On Linux systems, this is typically found under /opt/insightconnect or /usr/local/insightconnect. Check for the presence of the insightconnect service or CLI tools.
    Affected if InsightConnect is not installed on the system.
  2. Locate the ping plugin
    Navigate to the plugin directory within the InsightConnect installation. Ping plugins are typically stored under plugins/ or lib/ subdirectories. Search for directories or files containing 'ping' in the name.
    Affected if The ping plugin is not present in the installation.
  3. Identify the ping plugin version
    Examine the plugin manifest file (often named manifest.json, plugin.yaml, or VERSION) located within the ping plugin directory. Read the version field from this file.
    Affected if The version is lower than 1.0.4.
  4. Verify the operating system
    Run the command 'uname -s' or check /etc/os-release to confirm the underlying operating system is Linux. The vulnerability only affects the Linux version of the plugin.
    Affected if The operating system is not Linux.
  5. Check if ping action is configured
    Review the workflow or automation configurations within InsightConnect that utilize the ping action. Look for workflows or triggers that invoke the ping plugin with user-supplied host parameters.
    Affected if The ping action is actively used with external or user-controlled host input.

A system is affected if it runs Rapid7 InsightConnect with the ping plugin version below 1.0.4 on Linux and has the ping action configured with external host input.

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.4 or later
Fixed in 1.0.4
Interim mitigation

Implement strict input validation and use parameterized command execution (e.g., passing arguments safely rather than shell string concatenation) to ensure the host parameter cannot contain shell metacharacters or command separators.

Recommended fix Moderate confidence

1.0.4

  1. 1. Access the InsightConnect platform administration interface
  2. 2. Navigate to the Plugins or Integrations section
  3. 3. Locate the Ping plugin in the list of installed plugins
  4. 4. Check the current installed version of the Ping plugin
  5. 5. If version is below 1.0.4, locate the upgrade option for the Ping plugin
  6. 6. Initiate the upgrade to version 1.0.4
  7. 7. Verify the upgrade completed successfully by confirming the new version number
  8. 8. Test the Ping functionality to ensure the plugin operates correctly after the upgrade

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

Fix this in Insightconnect Ping 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-8660 — 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-8660 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