# CVE-2026-71965: CyberPanel 2.4.3 Authenticated RCE via Remote Backup Feature

> Authenticated attackers can achieve root-level remote code execution by exploiting unverified SSH key retrieval in the remote backup feature.

- **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-5hg3-c77v-8mxm

## What is CVE-2026-71965?

CVE-2026-71965 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 remote code execution vulnerability in the remote backup feature that allows authenticated attackers to gain root-level SSH access by supplying a malicious remote server address. Attackers can exploit the unverified SSH public key retrieval process to write an attacker-controlled public key directly to /root/.ssh/authorized_keys, granting persistent root access to the host system.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-71965 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71965 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: There is no known exploitation of CVE-2026-71965 in the wild and no public exploit code.

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-71965/ (Markdown: https://insights.sbomify.com/CVE-2026-71965/index.md)
```

## Sources

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

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