# CVE-2024-53706: Privilege escalation in SonicOS

> A remote authenticated low-privileged attacker can elevate privileges to root and execute code on the SonicOS Cloud platform.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-r2cp-qxjw-69v8

## What is CVE-2024-53706?

CVE-2024-53706 is a high-severity vulnerability in SonicWall SonicOS, published on 9 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Gen7 SonicOS Cloud platform NSv, allows a remote authenticated local low-privileged attacker to elevate privileges to `root` and potentially lead to code execution.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-53706?


## How do I fix CVE-2024-53706?

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

## Is CVE-2024-53706 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53706 and fix it if it is affected.

What it is: CVE-2024-53706 is a high-severity vulnerability in SonicWall SonicOS, published on 9 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53706 in the wild and no public exploit code.

Affected product: SonicWall SonicOS. 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-2024-53706/ (Markdown: https://insights.sbomify.com/CVE-2024-53706/index.md)
```

## Sources

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

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