« All news

In depth

Attackers probe max-severity SonicWall SMA1000 flaw days after patch, with no confirmed victims so far

Since 8 October two threat intelligence firms have seen attempts to exploit CVE-2026-102255, a CVSS 10.0 unauthenticated SSRF in SonicWall SMA1000 gateways, with one counting 135 hits on its decoys. No breach has been confirmed, but this is the third round of serious flaws in the product in 2026, there is no workaround to the hotfix and Shadowserver sees more than 400 exposed appliances.

What happened

On 6 October SonicWall released hotfixes for four vulnerabilities in its SMA1000 remote access gateways, bundled in advisory SNWLID-2026-0017. The most serious, CVE-2026-102255, is a server-side request forgery (SSRF) that requires no authentication. According to the advisory from the Centre for Cybersecurity Belgium (CCB), which cites the vendor, an unintended alternate access path in the Work Place interface turns the appliance into a forwarding proxy: an attacker without credentials can make the gateway send requests on their behalf and reach internal functions. It carries the maximum score, CVSS 10.0.

When the advisory went out, SonicWall said it had no evidence of exploitation, as Help Net Security reported. Two days later, threat intelligence firms Defused and Previdian began seeing malicious traffic against their honeypots. By 12 October Previdian had logged 135 attempts from two US IP addresses, according to The Hacker News.

The same advisory fixes a post-authentication command injection requiring admin rights (CVE-2026-102256, CVSS 7.8) and a Zip Slip, a path traversal triggered when extracting archives, in the AMC management console (CVE-2026-102257, CVSS 7.2); both lead to remote code execution. The fourth is a stored XSS in the AMC (CVE-2026-102258, CVSS 5.5).

What is confirmed and what is not

The key distinction: the attacks observed so far hit decoys, not real organisations.

Why it matters

SMA1000 appliances sit at the network edge and are used by mid-sized and large enterprises, managed security service providers and government bodies, according to Help Net Security and BleepingComputer. The CCB warns an attacker could reach internal systems and sensitive data, change the appliance configuration or disrupt remote access. SOCRadar cautions that it has not been shown that the SSRF alone allows code execution or full device compromise: that depends on which internal services the appliance can reach.

Recent history adds weight. In July attackers spent weeks exploiting two SMA1000 zero-days to deploy custom malware, and CISA later tied some of those attacks to ransomware gangs, BleepingComputer reported. In September SonicWall confirmed exploitation of another pre-authentication SSRF in Work Place, also rated CVSS 10.0. Previdian says the current attempts target the same interface using a different technique.

BleepingComputer notes that CISA has added 19 SonicWall flaws to its KEV catalogue in four years, 13 of them flagged as used by ransomware. Shadowserver counts more than 400 internet-exposed SMA1000 devices, though it is unclear how many are honeypots or already patched.

Timeline

Three rounds of serious flaws in the same product in roughly three months.

  1. July 2026zero-days CVE-2026-15409 and CVE-2026-15410 exploited for weeks (BleepingComputer).
  2. 1 SeptemberSonicWall publishes SNWLID-2026-0016 and confirms exploitation of CVE-2026-83548 and CVE-2026-83549 (Rapid7, Field Effect).
  3. 6 OctoberSonicWall publishes SNWLID-2026-0017 with hotfixes, citing no evidence of exploitation.
  4. 7 Octoberthe CCB issues its advisory urging immediate patching.
  5. 8 Octoberfirst malicious traffic hits Defused and Previdian decoys.
  6. 9 Octoberboth firms go public and BleepingComputer reports exploitation.
  7. 12 Octoberthe CCB adds its active exploitation note; The Hacker News reports 135 attempts.
  8. 13 OctoberSonicWall's advisory still does not acknowledge exploitation, per eSecurity Planet.

What organisations can do

The hotfix is the only fix. Everything else is about finding out whether someone got in first.

What to watch next

The decisive question is whether a real victim emerges. So far nobody has shown that a production SMA1000 was compromised, or that attackers are chaining the SSRF with CVE-2026-102256 or CVE-2026-102257 to run code. No public exploit has been found either.

Watch whether SonicWall updates its advisory to acknowledge exploitation and whether CISA adds the CVE to its KEV catalogue; as of 14 October no inclusion has been reported, though the catalogue itself was not checked. Still unknown: how many of the 400-plus exposed devices remain unpatched, and who is behind the attempts.

Sources

Vulnerabilities (8)

CVESeverityActive exploitationPublishedNVD status
CVE-2026-15409Critical (10)⚠ Active exploitation7/14/2026Analyzed
CVE-2026-15410High (7.2)⚠ Active exploitation7/14/2026Analyzed
CVE-2026-102256High (7.8)—10/7/2026Awaiting Analysis
CVE-2026-102258Medium (6.1)—10/7/2026Awaiting Analysis
CVE-2026-83548Critical (10)⚠ Active exploitation9/1/2026Analyzed
CVE-2026-83549High (7.8)⚠ Active exploitation9/1/2026Analyzed
CVE-2026-102257High (7.2)—10/7/2026Awaiting Analysis
CVE-2026-102255Critical (10)—10/7/2026Awaiting Analysis

Claims are published by the criminal groups themselves and are unverified until the organisation or the press confirms them. Names of natural persons (sole traders, individual professionals) are anonymised under the GDPR. We never link to leak sites or stolen data. To request the removal or anonymisation of an entry, contact the site administrator.