# CVE-2026-8592: OS Command Injection in Rapid7 InsightConnect AWK Plugin

> Remote attackers can execute arbitrary OS commands via unsafe shell construction in the AWK plugin's process_string action.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-xqrw-3c79-7qc7

## What is CVE-2026-8592?

CVE-2026-8592 is a high-severity command injection vulnerability in Rapid7 InsightConnect AWK Plugin, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS Command Injection vulnerability in the process_string action of Rapid7 InsightConnect AWK Plugin on Linux allows remote attackers to execute arbitrary OS commands via the text or expression parameters due to unsafe shell command construction in the processing pipeline.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-8592?

It affects 1 product.


Products: Rapid7 Insightconnect Awk.

## How do I fix CVE-2026-8592?

No fix has been published for CVE-2026-8592 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8592 being exploited?

There is no known exploitation of CVE-2026-8592 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8592 and fix it if it is affected.

What it is: CVE-2026-8592 is a high-severity command injection vulnerability in Rapid7 InsightConnect AWK Plugin, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8592 in the wild and no public exploit code.

Affected product: Rapid7 InsightConnect AWK Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8592/ (Markdown: https://insights.sbomify.com/CVE-2026-8592/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8592
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8592
- OSV: https://osv.dev/vulnerability/CVE-2026-8592

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8592/
Summaries are generated and may contain mistakes; the official description above is the record.
