# CVE-2026-15409: SonicWall SMA1000 Appliances Server-Side Request Forgery

> Remote unauthenticated attackers can exploit SSRF in the SMA1000 Work Place interface to force the appliance to make unintended requests.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 14 Jul 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-35rc-2vcv-r6q5

## What is CVE-2026-15409?

CVE-2026-15409 is a critical server-side request forgery vulnerability in SonicWall SMA1000, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000 Appliance Work Place interface. A remote unauthenticated attacker could potentially cause the appliance to make requests to unintended location.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 3 products.


Products: Sonicwall Sma6210 Firmware, Sonicwall Sma7210 Firmware, Sonicwall Sma8200v.

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

No fix has been published for CVE-2026-15409 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Jul 2026.

## Is CVE-2026-15409 being exploited?

Yes. Attackers have exploited CVE-2026-15409 in the wild since at least 14 Jul 2026, including in ransomware campaigns.

Public exploit code:

- This repo contains a proof-of-concept exploit for CVE-2026-15409. It establishes non-root remote code execution on SonicWall SMA 1000 by implementing the Erlang protocol expected by localhost:1050 and tunneling it through the websocket for file r/w and arbitrary code execution via RPC calls. (github_poc): https://github.com/remmons-r7/rapid7-CVE-2026-15409
- CVE-2026-15409/15410 SonicWall SMA1000 multi-exploit Framework - SSRF→Erlang RPC→RCE→root privesc. Features: --detect safe check, --exec, --read-file, --privesc, --rpc, interactive shell, batch threading, file write, ws-url override, pipe support. KEV listed CVSS 10.0 actively exploited. Authorized testing only. Use Ethically, Stay Legal.  (github_poc): https://github.com/tc4dy/CVE-2026-15409-15410-Framework
- CVE-2026-15409 (github_poc): https://github.com/0xredash/CVE-2026-15409
- Proof-of-Concept exploit for CVE-2026-15409 (SonicWall SMA 1000 RCE) via Erlang distribution over WebSocket. Achieves unauthenticated remote code execution as couchdb user. (github_poc): https://github.com/Ch4120N/CVE-2026-15409
- SonicWall SMA1000 WorkPlace wsproxy SSRF Remote Command Execution (metasploit)
- CVE-2026-15409 - Dectect (github_poc): https://github.com/HORKimhab/CVE-2026-15409

## Other vulnerabilities in SonicWall SMA1000

- [CVE-2026-83548](https://insights.sbomify.com/CVE-2026-83548/): SonicWall SMA1000 Appliances Server-Side Request Forgery (critical 10.0, exploited in the wild)
- [CVE-2026-83549](https://insights.sbomify.com/CVE-2026-83549/): SonicWall SMA1000 Appliances OS Command Injection (high 7.8, exploited in the wild)
- [CVE-2026-15410](https://insights.sbomify.com/CVE-2026-15410/): SonicWall SMA1000 Appliances Code Injection (high 7.2, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15409 is a critical server-side request forgery vulnerability in SonicWall SMA1000, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-15409 in the wild since at least 14 Jul 2026, including in ransomware campaigns.

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

## Sources

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

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