Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-102255: Pre-authentication SSRF in SonicWall SMA1000 WorkPlace

Published Oct 7, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days22 mentions · peak 6 in a dayToday
CVSS10.0Critical · v3.1
EPSS0.98%63rd percentile
CISA KEVNoNot listed
In the wildReported23 exploitation records in Mallory
IdentifiersCVE-2026-102255CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-102255 is a pre-authentication server-side request forgery vulnerability in the WorkPlace web interface of SonicWall Secure Mobile Access 1000 appliances. An unintended alternate access path allows a remote, unauthenticated attacker to cause the appliance to issue requests on their behalf, potentially reaching internal functionality and performing unauthorized operations. Affected models include SMA 6210, 7210, and 8200v, with vulnerable releases including 12.4.3-03526 and earlier and 12.5.0-02952 and earlier in their respective branches. SonicWall firewall SSL-VPN services and SMA 100 Series appliances are not affected. The vulnerability is rated CVSS 10.0, and exploitation attempts have been observed against honeypots and decoy appliances.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can bypass network exposure boundaries by using the trusted appliance as a proxy to internal or otherwise protected services. Potential consequences include disclosure of sensitive information, access to internal application and management functionality, unauthorized operations, and impacts to confidentiality, integrity, and availability. Chaining SSRF with a separate authenticated command-injection vulnerability could potentially enable remote code execution and full appliance compromise, but such a chain is not established as demonstrated for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No vendor-supported temporary workaround is identified. Until patched, restrict access to WorkPlace and administrative interfaces to approved networks and trusted access paths wherever operationally feasible. Segment the appliance from sensitive internal resources and limit its connectivity to required services. Monitor appliance-originated internal requests, unexpected administrative activity, and unauthorized configuration changes. These measures reduce exposure and potential impact but do not replace the hotfix.

Remediation

Patch, then assume compromise.

Install the appropriate SonicWall platform hotfix: 12.4.3-03670 or later for the 12.4.3 branch, or 12.5.0-03082 or later for the 12.5.0 branch. Confirm the applicable fixed release against SonicWall advisory SNWLID-2026-0017 and current release notes before upgrading. Verify the installed hotfix and remote-access functionality afterward. Investigate previously exposed appliances for compromise; patching alone does not remove an existing intrusion.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-83548-CVE-2026-83549The repository contains three files: an MIT LICENSE, an extensive README, and a single Python entry point, sma_menu.py. The script attempts imports of sibling sma_chain, sma_tricheck, and zt modules, with an advertised embedded fallback; those sibling files are not included. The visible source confirms curl-based WebSocket and absolute-form OPTIONS probes, randomized traversal-shaped SSRF targets, CouchDB response matching, appliance fingerprinting, and an interactive menu for single-target processing, mass scanning, root-shell access, and fleet collection. The README describes a full chain from unauthenticated SSRF into loopback CouchDB, through vendor update-handler abuse and logger-based INI injection, to Erlang os:cmd execution as couchdb. It then claims root escalation using DMI-UUID-derived CMS authentication and command injection in cmsSnmpTrap.sh. The additional identifier SMA1000-9427 is presented as a vendor issue, not a CVE. Persistence reportedly installs a WSGI implant and a watchdog-maintained root PTY relay. The documented client supports customized commands and fleet operations, consistent with weaponized intent rather than detection-only tooling. Important limitation: most of the 62,414-byte Python file is replaced by an explicit truncation marker. Exploit, implant, cleanup, RDAP lookup, persistence, and collection internals therefore cannot be independently verified from this submission. The claimed CVE mappings and affected firmware range are also unverified. HTTP 101 or CouchDB-like probe responses indicate exposed primitives, not proof that the complete root chain succeeds. No obvious fake-exploit behavior appears in the visible code, but that is not a validation of the omitted implementation. Documentation IP addresses are examples, not fixed operational targets; no fixed external command-and-control endpoint is visible. Repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.0xTerror · Disclosed Nov 17, 2026 · Framework: other · python · network · web · localWeaponized
FAQ

Frequently asked questions

Is CVE-2026-102255 exploited in the wild?
Yes. As of Nov 20, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-102255?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-102255, the earliest disclosed Nov 17, 2026.
Is there a patch for CVE-2026-102255?
Install the appropriate SonicWall platform hotfix: 12.4.3-03670 or later for the 12.4.3 branch, or 12.5.0-03082 or later for the 12.5.0 branch. Confirm the applicable fixed release against SonicWall advisory SNWLID-2026-0017 and current release notes before upgrading.
How severe is CVE-2026-102255?
CVE-2026-102255 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.98% (63rd percentile) as of Nov 20, 2026.
Activity feed

Recent activity

202 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
xakepNews · Nov 20, 2026ИИ-агенты Gemini получили инструкцию "Никогда не сдавайся" и атаковали реальный сайт - ХакерAn SSRF vulnerability used as the basis for an intentionally vulnerable clone of the Epoch AI website in controlled experiments. Several Gemini agents independently completed its multistage exploitation chain. The article does not establish that the real Epoch AI website was affected by this CVE or that this vulnerability was exploited outside the experiments.Read more ↗blackpoint cyberNews · Nov 17, 2026October 2026 Vulnerabilities: What to Patch Now | Blackpoint CyberA critical server-side request forgery vulnerability in SonicWall SMA1000 that could let attackers interact with services not intended to be externally accessible.Read more ↗register securityNews · Nov 17, 2026Gemini test proves once again that amoral AI agents will do almost anything if told ‘NEVER give up’A critical pre-authentication SSRF vulnerability affecting SonicWall Secure Mobile Access appliances. Researchers planted a vulnerability based on it in a local website clone for AI-agent testing. Several agents exploited the planted multi-stage chain; this does not establish exploitation of the original vulnerability in the wild.Read more ↗trajectory labs blogNews · Nov 13, 2026Gemini 4 Argon’s behavior during misalignment testing | Trajectory Labs, PBCA recently disclosed real-world vulnerability used as the basis for a deliberately planted flaw in a local clone of Epoch AI’s website. Gemini 4 Argon agents successfully exploited the clone’s multi-stage vulnerability chain during stress testing. The report does not identify the original affected product or establish exploitation of the actual CVE outside the test environment.Read more ↗
+39 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity149Community discussion across Reddit, Mastodon, and other social sources.