Skip to content

Build Not yet confirmed elsewhere1 publisher 2 min read Published

Defused decoys logged exploit attempts on SonicWall's CVSS 10.0 SMA1000 flaw two days after disclosure

Defused researchers say first exploitation attempts reached their decoys on 8 October, two days after SonicWall disclosed its CVSS 10.0 SMA1000 flaw. The advisory, last updated 6 October, still says there is no evidence of exploitation.

The Engineer · Build desk

Send a correction

Illustration accompanying Defused decoys logged exploit attempts on SonicWall's CVSS 10.0 SMA1000 flaw two days after disclosure
Generated illustration
The other three flaws carry lower ratings Ratings for the four flaws in SonicWall's 6 October advisory; the other three set a higher bar for an attacker.

Ranking of the four SonicWall flaws by rating: pre-authentication SSRF in the SMA1000 Work Place interface 10.0; post-authentication OS command injection 7.8; Zip Slip path traversal in the Appliance Management Console 7.2; stored cross-site scripting 5.5.

The other three flaws carry lower ratings (Rating of each flaw in SonicWall's 6 October advisory)
RankItemValueClaim
1Pre-auth SSRF, Work Place10 rating5
2Post-auth OS command injection7.8 rating8
3Zip Slip path traversal7.2 rating8
4Stored cross-site scripting5.5 rating8

What happened

  • SonicWall's advisory SNWLID-2026-0017 covers four flaws, and the top one, CVE-2026-102255, is a pre-authentication server-side request forgery in the SMA1000 Work Place interface.
  • Models 6210, 7210 and 8200v are affected on 12.4.3-03526 or older and on 12.5.0-02952 or older, with fixes in 12.4.3-03670 and 12.5.0-03082 and higher.
  • Beazley Security says attackers exploited earlier SSRF flaws in the same Work Place interface as zero-days, disclosed by SonicWall in July and again in September.

Why it matters

  • Who has to decide decision Owners who installed 12.5.0-02952, the September fix, are on an affected build and need a second upgrade on the same interface.
  • What it limits constraint The advisory's workaround field reads none, so an owner who cannot patch at once has no vendor-listed stopgap.
  • What doesn't add up contradiction SonicWall's no-evidence line speaks to what it knows about customer appliances, while the decoy logs show attackers trying. Neither source shows a production appliance was compromised.

SonicWall labels CVE-2026-102255 both an SSRF and an unintended-proxy flaw, the CWE-441 confused-deputy pattern [7]. The cause is an unintended alternate access path, and the result is an appliance that forwards the attacker's requests [7]. Placement matters here. SMA1000 units sit at the network edge so that staff and partners can reach internal systems from outside [4]. In our view, a forward proxy on that box inherits the box's reach into the internal network.

The port is the new information. According to the DEV Community write-up, the payload captured by a research honeypot aimed a request at a local service on port 5984 [18]. The write-up does not say what listens on that port or whether a stock SMA1000 exposes anything there. A decoy shows what the attacker asked for, not what a real appliance would have answered. For the observation to transfer, a real service would have to sit on that port and the SSRF would have to reach it. We would not assume either.

We would still read the payload as intent, since someone wrote a request with a specific internal target within two days of disclosure [c3, c5]. That is a reason to patch sooner. The fix itself is unchanged.

No proof-of-concept is known, and SonicWall has published no technical detail beyond the advisory text [14]. The advisory page was captured on 13 October, five days after the first decoy hits, with its last-updated date still at 6 October [c17, d2].

The Work Place interface has now produced three rounds of urgent patching in 2026 [15]. CISA listed the two September flaws in its Known Exploited Vulnerabilities catalogue on 2 September [12], and this advisory arrived 34 days later [17].

Scope is narrow. SonicWall says SSL-VPN on its firewall products is not affected, and Help Net Security reports the SMA 100 series is not either [10]. The other three flaws in the advisory carry ratings of 7.8, 7.2 and 5.5 and a higher bar for an attacker [8].

What to watch

  • Whether SonicWall revises the advisory's exploitation status, which was last updated on 6 October.
  • Whether Defused or anyone else publishes the payload and says what listens on port 5984 on a real SMA1000.
  • Whether CISA adds CVE-2026-102255 to its Known Exploited Vulnerabilities catalogue, as it did for the September pair.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence62
Adoption
Not scored
Hype gap+8
Incentives
Not scored
Confidence60
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Researchers at Defused reported that the first exploitation attempts reached their decoys on 8 October, two days after disclosure.

    Reported Supported Source: Defused researchers, as reported by DEV Community2 sources— create a free account to open themView cited source
  2. [2]

    SonicWall's advisory, last updated on 6 October, states there is currently no evidence any of the four flaws are being exploited in the wild.

    Reported Supported Source: SonicWall advisory, as reported by DEV Community2 sources— create a free account to open themView cited source
  3. [3]

    The advisory page, with a publication and last-updated date of 6 October 2026, was captured on 13 October 2026.

    Reported Supported Source: DEV Community write-up2 sources— create a free account to open themView cited source

Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.

Add to ChatGPTAdd to Claude

Sources

1 independent publisher whose own reporting we read for this story.

  1. dev.to

    1 article · October 16, 2026

    SonicWall's SMA1000 SSRF Reached Security Decoys Two Days After the Patch

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Loading related stories