# CVE-2026-86299: Linksys RE7000 PingTest json.cgi platform_event_pingTest os command injection

> Remote attackers can execute arbitrary OS commands on Linksys RE7000 devices via the PingTest handler, requiring specific permissions.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **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:** 7 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-8gm9-6v5q-x2cp

## What is CVE-2026-86299?

CVE-2026-86299 is a critical command injection vulnerability in Linksys RE7000, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in Linksys RE7000 2.0.15. This affects the function platform_event_pingTest of the file /cgi-bin/json.cgi?PingTest of the component PingTest Handler. The manipulation of the argument pingTestIp/pingTestPktSize/pingTestTimes results in os command injection. The attack can be launched remotely. The exploit is now public and may be used.

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

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


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

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

## Is CVE-2026-86299 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86299 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86299 is a critical command injection vulnerability in Linksys RE7000, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86299 exists.

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

## Sources

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

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