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

> A remote unauthenticated attacker can exploit an SSRF vulnerability in the SMA1000 Work Place interface to access sensitive functionality and perform unauthorized operations.

- **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 2 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-ghw2-cfh2-xvgc

## What is CVE-2026-83548?

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

### Official description

A Pre-authentication SSRF vulnerability exists in the SMA1000 Appliance Work Place interface due to an unintended alternate access path. A remote unauthenticated attacker could potentially exploit this vulnerability to gain unauthorized access to sensitive functionality and perform unauthorized operations.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-441 (Unintended Proxy or Intermediary)

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

It affects 3 products.


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

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

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

## Is CVE-2026-83548 being exploited?

Yes. Attackers have exploited CVE-2026-83548 in the wild since at least 2 Sep 2026.

Public exploit code:

- SonicWall SMA1000 WorkPlace SSRF to Root Remote Code Execution (metasploit)
- Vulnerability Analysis of CVE-2026-83548 affecting SonicWall SMA1000 security systems. (github_poc): https://github.com/xoessie/CVE-2026-83548-SonicWall-SMA1000-Analysis
- Non-intrusive detector for SonicWall SMA 1000 exposure to CVE-2026-83548/-83549 (version/patch-state check; no exploitation) (github_poc): https://github.com/xcoy0te/CVE-2026-83548-checker
- CVE-2026-83548, CVE-2026-83549, - Draft or TODO - https://github.com/rapid7/metasploit-framework/pull/21883 (github_poc): https://github.com/HORKimhab/CVE-2026-83548-CVE-2026-83549
- CVE-2026-83548 — SonicWall SMA1000 Work Place pre-auth SSRF (github_poc): https://github.com/maxprog-svg/CVE-2026-83548
- SonicWall SMA1000 WorkPlace - Unauthenticated SSRF to CouchDB (nuclei)

## Other vulnerabilities in SonicWall SMA1000

- [CVE-2026-15409](https://insights.sbomify.com/CVE-2026-15409/): 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-83548 and fix it if it is affected.

What it is: CVE-2026-83548 is a critical server-side request forgery vulnerability in SonicWall SMA1000, published on 1 Sep 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-83548 in the wild since at least 2 Sep 2026.

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

## Sources

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

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