Skip to main content
All incident reports
Incident report

SonicWall SMA 1000 flaw, rated 10, exploited within days of patches

A pre-authentication server-side request forgery flaw in SonicWall's Secure Mobile Access (SMA) 1000 appliances, rated 10.0 on the CVSS severity scale, drew exploitation attempts two days after patches shipped. Researchers counted 135 attempts from two US IP addresses, while SonicWall's advisory still recorded no evidence of exploitation.

· First published

The short version

  • The flaw. CVE-2026-102255 is a pre-authentication server-side request forgery bug in SonicWall SMA 1000 remote-access appliances, rated 10.0 on the CVSS scale. It lets an unauthenticated attacker make the appliance send requests on their behalf and reach internal functionality.
  • Exploitation. Defused Cyber and Previdian first saw signs of exploitation on 8 October, two days after patches shipped. Previdian counted 135 attempts from two unique IP addresses in the US.
  • Vendor position. SecurityWeek reported on 8 October that SonicWall had no evidence the patched flaws were being exploited in the wild. As of 12 October its advisory had not been updated to record the attempts.
  • Earlier zero-days. Two other SMA 1000 flaws were used as zero-days in June 2026 by an actor tracked as UTA0533. Rapid7 says the attackers took credentials, active session databases and multi-factor seeds off the appliances and moved into internal networks.

Timeline

DateEvent
June 2026Two other SMA 1000 flaws, CVE-2026-15409 and CVE-2026-15410, are exploited as zero-days by an actor tracked as UTA0533.
6 OctoberSonicWall releases patches for CVE-2026-102255, according to The Hacker News.
8 OctoberDefused Cyber and Previdian detect the first signs of exploitation attempts.
8 OctoberSecurityWeek reports the SonicWall patch release; SonicWall says it has no evidence any of the flaws are exploited in the wild.
12 OctoberPrevidian data shows 135 attempts from two US IP addresses, and SonicWall's advisory still does not mention exploitation.

The flaw and the fix

SonicWall shipped fixes for four vulnerabilities in its Secure Mobile Access (SMA) 1000 appliances, a family of remote-access gateways. The most severe, CVE-2026-102255, carries a CVSS score of 10.0 and is a pre-authentication server-side request forgery (SSRF) flaw arising from an unintended alternate access path. In SSRF the attacker does not log in; they make the device issue requests on their behalf. SonicWall says this could reach internal functionality and allow unauthorised operations.

One of the fixed builds is 12.5.0-03082, and SonicWall urged customers to install the updates as soon as possible, noting that SSL-VPN on its firewall products is not affected. The same release addressed two high-severity and one medium-severity issue that could be used for remote code execution and cross-site scripting. The Hacker News dates the patch release to 6 October; SecurityWeek reported the announcement on 8 October.

Exploitation within days

Defused Cyber and Previdian spotted the first signs of exploitation on 8 October, two days after the patches appeared, according to The Hacker News. Previdian's data shows 135 attempts to date, coming from two unique IP addresses located in the US. The report does not say whether any attempt succeeded.

SonicWall had not updated its advisory to reflect the exploitation as of 12 October, the article says. SecurityWeek, reporting on 8 October, quoted the company saying it had no evidence the patched vulnerabilities were being exploited in the wild. Neither the two US addresses nor the actor behind them is identified in the sources.

Earlier zero-days in the same appliance

In June 2026 two other SMA 1000 flaws, CVE-2026-15409 (rated 10.0) and CVE-2026-15410 (rated 7.2), were used as zero-days by an actor The Hacker News calls UTA0533, which deployed Java web shells and malware named KNUCKLEBALL. Rapid7 said the attackers used internet-facing devices as an initial access route, then extracted credentials, active session databases and Time-Based One-Time Password (TOTP) multi-factor seed configurations before moving into internal networks. No source says whether the October attempts involve the same actor.

SecurityWeek's 8 October article also covered Splunk patches for flaws in Splunk Enterprise, MCP Server and an add-on for Amazon Web Services. No source links those fixes to the SonicWall flaw, and they are treated here as a separate matter.

What is not known yet

  • Who is behind the exploitation attempts and whether the two US IP addresses are the attackers' own infrastructure or relays.
  • Whether any of the 135 attempts succeeded, and whether any SMA 1000 appliance has been compromised since 6 October.
  • How many SMA 1000 appliances are reachable from the internet or still running a vulnerable build.
  • Whether the actor behind the June 2026 zero-days, UTA0533, is also responsible for the October attempts.
  • Whether SonicWall will change its advisory to record the exploitation, and whether it has investigated the reported attempts.

What to do

If you run SonicWall SMA 1000

  1. Update appliances to build 12.5.0-03082; SonicWall's advisory gives the other fixed build and its installation guidance.
  2. Check the appliance for requests to internal systems that it should not be making, which is the behaviour the SSRF flaw lets an unauthenticated attacker trigger.
  3. Treat an internet-facing appliance that has been unpatched since 6 October as potentially compromised and look for unusual internal or outbound requests from it.

If an SMA 1000 was exposed in June 2026

  1. Rotate the credentials, active session data and TOTP multi-factor seeds that were stored on or reachable through the appliance; Rapid7 says attackers extracted all three in the earlier campaign.
  2. Look for lateral movement from the appliance into the internal network, which Rapid7 says followed that credential theft.

For everyone else

  1. Keep an inventory of internet-facing appliances and patch maximum-severity pre-authentication flaws first; this one drew attempts within two days of its fix.
  2. Expect scanning and exploitation attempts as soon as an unauthenticated flaw in an edge device becomes public, and check for them even before the vendor's advisory records them.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.