CVE-2026-8665
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 · uneditedOS Command Injection vulnerability in the TR action of Rapid7 InsightConnect Translate Plugin on Linux allows remote attackers to execute arbitrary OS commands via the text or expression parameters due to insufficient input sanitization in shell command construction.
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 confidenceOS Command Injection vulnerability in the TR action of Rapid7 InsightConnect Translate Plugin on Linux allows remote attackers to execute arbitrary OS commands via the text or expression parameters due to insufficient input sanitization in shell command construction.
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< 2.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Rapid7 InsightConnect is deployedCheck for InsightConnect installation directory, service, or plugin registry. Common locations: /opt/insightconnect, /var/lib/insightconnect, or consult InsightConnect documentation for your deployment method.Affected if InsightConnect is not installed - not affected. If installed, continue to next check.
-
Verify Translate Plugin is installedList installed plugins in InsightConnect. This is typically done via the InsightConnect UI under Plugins section, or via CLI/API if available in your deployment: insightconnect-cli plugin list or check the plugins directory.Affected if Translate Plugin is not installed - not affected. If installed, continue to next check.
-
Check Translate Plugin versionView the installed version of the Translate Plugin. In the InsightConnect UI, go to Plugins > Translate > Version. If using CLI: insightconnect-cli plugin get translate or check the plugin manifest file.Affected if Version is 2.0.3 or higher - not affected. Version is below 2.0.3 or version cannot be determined - potentially affected, continue to next check.
-
Confirm environment is LinuxCheck the operating system where InsightConnect and the Translate Plugin are running. Run: uname -a or cat /etc/os-release.Affected if Running on Windows or macOS - not affected (vulnerability is Linux-specific). Running on Linux - potentially affected, continue to next check.
-
Check if TR action is enabled or usedReview workflow configurations and action usage logs for the Translate Plugin TR action. Check workflow definitions that include the Translate plugin and specifically the TR action. Inspect audit logs or activity logs for TR action execution.Affected if TR action is not configured in any workflow and has never been executed - not affected. TR action is enabled or has been used - potentially affected.
The environment is affected if Rapid7 InsightConnect with Translate Plugin version below 2.0.3 is running on Linux and the TR action is enabled or has been used with user-supplied text or expression parameters.
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 · scoped2.0.3
Upgrade to a patched version of the Translate Plugin. Until a patch is available, implement strict input validation and avoid direct shell command execution with user-supplied parameters, or disable the TR action if not essential.
2.0.3
- Log into the InsightConnect management console
- Navigate to the Plugins or Integrations section
- Locate the Translate plugin in the installed plugins list
- Check the current version to confirm it is below 2.0.3
- Update the Translate plugin to version 2.0.3 or later
- Verify the upgrade was successful by confirming the installed version is 2.0.3 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8665 — 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-2026-8665 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