# CVE-2026-74237: GFI Exinda AI / ClearView < 7.6.5 Argument Injection via Tools Iperf Client

> An authenticated attacker can inject arguments into the iperf command to read arbitrary files and exfiltrate data to an external server.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-f2hc-mh59-36hc

## What is CVE-2026-74237?

CVE-2026-74237 is a high-severity command injection vulnerability in GFI ClearView, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GFI Exinda AI and ClearView before 7.6.5 contains an argument injection vulnerability in the Tools Iperf Client functionality. The web_tools_cmd() function constructs an iperf command using the server and options parameters without sanitization, permitting injection of arbitrary iperf flags. An authenticated attacker with Unprivileged (lowest-level) access can supply the iperf -F flag to read an arbitrary file from the system and transmit its contents to an attacker-controlled server.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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


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

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

## Is CVE-2026-74237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74237 is a high-severity command injection vulnerability in GFI ClearView, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74237 in the wild and no public exploit code.

Affected product: GFI ClearView. 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-74237/ (Markdown: https://insights.sbomify.com/CVE-2026-74237/index.md)
```

## Sources

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

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