SMA1000 WorkPlace

CVE-2026-15409: SonicWall SMA1000 zero-day tunnels attackers to internal services

An unauthenticated WebSocket bypass in the SMA1000 WorkPlace portal reaches localhost-only services (CVSS 10), and attackers chained it with CVE-2026-15410 for root. Exploited since June 22, 2026; CISA flags ransomware use.

Published Updated

ExploitedYes, in CISA KEVAdded 14 Jul 2026
Ransomware useKnownPer CISA
SeverityCRITICALCVSS 3.1 10
EPSS6.8%Chance of exploitation in 30 days
Public exploitYes
FixAvailable

Affected and fixed versions

Product / branchFixed in
SMA1000 12.5.0-02283, 12.5.0-02624, 12.5.0-0280012.5.0-02835 or later; install 12.5.0-03082, which also fixes later flaws
SMA1000 12.4.3-03245, 12.4.3-03387, 12.4.3-0343412.4.3-03453 or later; install 12.4.3-03670, which also fixes later flaws
SSL-VPN on SonicWall firewalls, SMA 100 SeriesNot affected

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

The SMA1000 WorkPlace portal has a WebSocket endpoint, /wsproxy, that tunnels a logged-in user’s traffic to internal hosts. On affected hotfixes, a request with the user agent SMA Connect Agent and a bmID value starting with -3389 gets a tunnel without any session, and can point it at 0.0.0.0 or localhost (Volexity). That exposes services meant to be reachable only from the appliance itself:

  • CouchDB on port 1050, which ships with the credentials admin:admin.
  • The control service (ctrl-service) on port 8188, which runs system operations as root.

Attackers chained this with CVE-2026-15410. Through CouchDB they wrote a script that read the appliance’s hardware UUID, which is the control service’s password. They then called the control service’s hotfix-removal function with a path-traversal name like ../../../../../tmp/1234.sh, which ran their script as root. Volexity also found that many physical appliances share the same default UUID, which on its own would unlock the control service.

With root, the actor Volexity calls UTA0533 planted custom implants that survive reboots, sniffed LDAP traffic for domain passwords, and used the appliance to authenticate to internal systems. Rapid7 saw theft of credentials, session databases and TOTP MFA seeds, and logons to domain controllers. Resecurity says INC ransomware has since become the main actor using the chain, and CISA has flagged both CVEs as used in ransomware campaigns.

Am I affected?

You’re affected if you run an SMA1000 6210, 7210 or 8200v on any of these platform hotfixes:

  • 12.4.3-03245, 12.4.3-03387 or 12.4.3-03434
  • 12.5.0-02283, 12.5.0-02624 or 12.5.0-02800

The attack needs only network access to the WorkPlace interface’s /wsproxy endpoint. No credentials and no special configuration are required.

SSL-VPN on SonicWall firewalls and the SMA 100 Series are not affected.

What to do

1. Install the newest hotfix: 12.4.3-03670 or 12.5.0-03082 (or later) from MySonicWall. July’s 12.4.3-03453 and 12.5.0-02835 fix this CVE but are vulnerable to CVE-2026-83548, a second WorkPlace SSRF exploited in September, and to CVE-2026-102255, fixed in October. There is no workaround.

2. Check for compromise, whatever your patch date. Exploitation started at least three weeks before the advisory, and a patched appliance can still carry implants. Use SonicWall’s log checks and Volexity’s file checks below.

3. If you find any indicator, SonicWall says to:

  • Re-image hardware appliances, or redeploy virtual ones. Don’t clean in place: the implants patch running Java processes and edit startup scripts.
  • Change all user and administrator passwords.
  • Reset every user’s TOTP token. Attackers stole the MFA seeds, so old tokens are no longer a second factor.

Also rotate the LDAP or AD service account the appliance uses. Rapid7 saw attackers log on to domain controllers with it, and Volexity saw LDAP traffic captured. Review Windows logons from the appliance’s internal IP (below) and treat matches as a network intrusion. Resecurity reports INC ransomware victims also got calls and emails from “helpers” offering to resolve the incident. Route those to your incident response team and law enforcement.

Detection

SonicWall’s indicators (from the advisory):

  • In /var/log/aventail/extraweb_access.log: requests to /__api__/login or /__api__/logout with status 200. These paths don’t exist on a clean appliance.
  • In the same log: requests to /wsproxy with status 101 and suspicious host values, such as 0.0.0.0, localhost or ::ffff:127.0.0.1, often with bmID=-3389..., serviceType=SSH and port=1050 or port=8188. Rapid7 also saw serviceType=TELNET.
  • In /var/log/aventail/ctrl-service.log: hotfix rollbacks with path-traversal names, such as running hotfix removal for:../../../../../tmp/1234.sh.
  • In /var/lib/unit/conf.json: routes for /__api__/login or /__api__/logout. Volexity found them proxied to http://127.0.0.1:8085.

On the appliance (Volexity):

  • WebSocket connections to host = 0.0.0.0 and port =1050 (or 8188) in /var/log/aventail/access_servers.log.
  • Unexpected setuid binaries. Run find / -perm -4000 and compare with Volexity’s list of legitimate ones. /usr/bin/xzfind is the attacker’s.
  • python3 /usr/lib/python3.11/site-packages/deploy_new.py added to /etc/init.d/workplace.
  • Unexpected files in /tmp and /var/tmp, especially owned by the couchdb user, and tcpdump capture files.
  • Requests to /workplace/error.jsp or /workplace/dialogs/errorDialog.jsp with the fake Mozilla/6.0 ... Chrome/149.0.0.1 user agent.

In your network (Rapid7):

  • Windows event 4624, logon type 3, from the appliance’s internal IP to domain controllers or other servers, with no matching VPN session and workstation names like kali or DESKTOP-....
  • Access to /tmp/temp.db* on the appliance, which holds session data.
  • Probes for /auth1.html, /.env and /api/sonicos/is-sslvpn-enabled from the IP ranges listed above.

Indicators of compromise

Rapid7's addresses belong to one hosting provider, F.N.S Holdings Limited (AS206092); Rapid7 suggests blocking it if you have no business need. The log entries in SonicWall's own advisory are the most reliable signs; see Detection.

The .txt list has one IP per line and a fixed address, so a firewall can pull it as an External Dynamic List: https://patchtonight.com/iocs/CVE-2026-15409.txt

IndicatorTypeReported by
45.131.194[.]0/24IPF.N.S Holdings Limited, AS206092Rapid7
45.146.54[.]0/24IPF.N.S Holdings Limited, AS206092Rapid7
63.135.161[.]0/24IPF.N.S Holdings Limited, AS206092Rapid7
173.239.211[.]0/24IPF.N.S Holdings Limited, AS206092Rapid7
193.37.32[.]179IPRapid7
193.37.32[.]214IPRapid7
216.73.163[.]151IPRapid7
216.73.163[.]158IPRapid7
DESKTOP-KRLUI3JHost nameAttacker workstation name in Windows logonsRapid7
DESKTOP-IC3C80FHost nameAttacker workstation name in Windows logonsRapid7
DESKTOP-5P0TSCPHost nameAttacker workstation name in Windows logonsRapid7
KALIHost nameAttacker workstation name in Windows logonsRapid7
SMA Connect AgentUser agentUsed on /wsproxy exploit requests (also the legitimate client's name)Volexity
Mozilla/6.0 (Windows NT 11.0; Win64; x64) AppleWebKit/1537.136 (KHTML, like Gecko) Chrome/149.0.0.1 Safari/1537.136User agentUnlocks the Suo5 and ORANGETAIL implantsVolexity
81a9af3846bad3a1107164ff7cf0a08e020b31a3b32fd17866e17d4c1565f7f2SHA-256ROOTRUN setuid helper, /usr/bin/xzfind (SHA-256)Volexity
8c470301dcb7278f73e622f1950073567b34011c64b60cdfbb0f89803923a5a3SHA-256KNUCKLEBALL loader, deploy_new.py (SHA-256)Volexity
1e1e68bbb899450a57274a8b12082ed4e2040a2aae77014f20431689d2b4edeeSHA-256Suo5 proxy, agent_wp8.jar (SHA-256)Volexity
ea9154e374e4f77bc2cf54282e23543573980342a85bc888cb23f20b8bbba081SHA-256ORANGETAIL web shell, agent_wp9.jar (SHA-256)Volexity
/usr/bin/xzfindFile pathROOTRUN setuid binaryVolexity
/usr/lib/python3.11/site-packages/deploy_new.pyFile pathKNUCKLEBALL, started from /etc/init.d/workplaceVolexity
/tmp/hypdate.b64File pathEncoded CVE-2026-15410 exploitVolexity
/tmp/1234.shFile pathScript run as root through remove_hotfixVolexity
/tmp/agent_wp8.jarFile pathVolexity
/tmp/agent_wp9.jarFile pathVolexity
/var/tmp/lib.shFile pathStarts tcpdump to capture LDAP trafficVolexity
info@helprans[.]comEmailExtortion contact given to INC ransomware victimsResecurity
helprans[.]comDomainRegistered 2 June 2026Resecurity

Volexity's YARA rules for ROOTRUN, KNUCKLEBALL and ORANGETAIL.

Sources

Page changelog

  • Full analysis published.

KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.