# CVE-2026-71966: CyberPanel 2.4.3 Authenticated Command Injection via starRemoteTransfer

> Authenticated attackers can execute arbitrary OS commands in CyberPanel by injecting malicious code via remote backup transfer API responses.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 10 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-hmw4-vv3v-9326

## What is CVE-2026-71966?

CVE-2026-71966 is a high-severity command injection vulnerability in usmannasir cyberpanel, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CyberPanel 2.4.3, fixed in commit eca0c3c, contains an authenticated command injection vulnerability in the remote backup transfer feature that allows authenticated attackers to execute arbitrary OS commands by controlling a remote server's API response. Attackers can inject malicious commands through a crafted directory name in the remote server's API response, which bypasses security middleware validation and is passed unsanitized to the OS command execution function.

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

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


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

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

## Is CVE-2026-71966 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71966 is a high-severity command injection vulnerability in usmannasir cyberpanel, published on 10 Aug 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-71966 exists.

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

## Sources

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

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