Three SSRFs, three fix builds: the SonicWall SMA1000 patched state has expired twice this year
CVE-2026-102255, a pre-authentication server-side request forgery in the SMA1000 Work Place interface, drew exploitation attempts within days of its 6 October fix. It is the third such flaw in that interface since July, and each new advisory lists the previous fix build as vulnerable.

A fix that lasted five weeks
On 6 October SonicWall released hotfixes for four vulnerabilities in its SMA1000 remote access appliances [5]. The most serious, CVE-2026-102255, is a pre-authentication server-side request forgery in the Work Place user portal, rated 10.0 [1][9]. The vendor’s notice said there was no evidence of exploitation [1]. Within two to three days, sensor operators reported attempts against it [2][3][4].
The more important finding is in the version tables. The October advisory lists 12.4.3-03526 and 12.5.0-02952 and earlier as affected [1]. Those are the builds SonicWall shipped on 1 September to close the previous zero-day [6]. The September advisory, in turn, listed the July fix builds, 12.4.3-03453 and 12.5.0-02835, as affected [6][7]. Twice this year, an SMA1000 appliance that was fully patched became vulnerable again within roughly five to seven weeks, without any change on the appliance.
Three flaws in one interface
The sequence began in July. CVE-2026-15409, a pre-authentication SSRF in the Work Place interface, was disclosed on 14 July and added to the CISA Known Exploited Vulnerabilities catalog the same day with a three-day remediation deadline [11][12]. Volexity’s investigation found that a request-proxying function let external traffic reach services bound only to the appliance’s local interface [8]. The actor used those services to write and run files, then used a further flaw to obtain root [8]. Volexity traced the earliest activity to 22 June, more than three weeks before disclosure [8]. CISA later flagged both July CVEs as used in ransomware campaigns [12][13].
The second flaw, CVE-2026-83548, followed on 1 September. SonicWall described it as a pre-authentication SSRF through an unintended forward proxy, confirmed as actively exploited, and exploited alongside a post-authentication command execution flaw; Beazley Security reports the two were chained [6][14]. CISA added both on 2 September with a 5 September deadline and marked them for forensic triage [10][12].
CVE-2026-102255 is described as an SSRF arising from an unintended alternate access path, which lets an unauthenticated attacker make the appliance issue requests on its behalf and reach internal functions [1][9]. Beazley Security reports that SonicWall characterises it as closely mirroring the September flaw, and that the vendor has not said whether it is a variant or a bypass of that fix [14]. The CWE assignments for the September and October records are identical [9][10]. All three SSRFs carry the same 10.0 vector in the public record [9][10][11].
The October release also fixed three post-authentication flaws: an operating system command injection rated 7.8, a path traversal in the management console rated 7.2 and stored cross-site scripting rated 5.5 [1]. The July and September waves each paired a pre-authentication SSRF with a post-authentication execution flaw, and in both cases researchers report the pair was chained to code execution without credentials [7][8][14]. The October release has the same shape. No chain involving the October flaws has been published, but that pairing is why the SSRF rating matters more than its standalone description suggests.
What the exploitation data shows
The evidence for CVE-2026-102255 comes from deception infrastructure. Defused reported unauthenticated SSRF traffic against its SMA decoys from 8 October [3][4]. Previdian records its first observation on 9 October and 135 attempts from two source addresses against one sensor by 10 October, with a confirmed exploitation verdict [2]. Previdian’s founder told BleepingComputer it was unknown whether those attempts would have compromised real systems [3]. The attempts targeted an internal database service through the appliance [3], the same class of internal service reached in July [8].
The two first-seen dates differ because the sensors differ, and neither establishes successful compromise. As of the latest retrieval, CVE-2026-102255 was not in the KEV catalog [2][12], and the vendor notice had not been updated to acknowledge exploitation [1][5]. Exposure figures also vary: Shadowserver data cited in August gave more than 380 internet-facing SMA1000 appliances, and data cited in October gave more than 400 [3][13]. Neither figure distinguishes patched devices or honeypots.
The public record disagrees
Defenders reading national advisories rather than the vendor notice may reach the wrong build. Singapore’s Cyber Security Agency alert of 8 October, last updated on 12 October and re-checked on 13 October, lists the correct affected range but advises updating to 12.4.3-03453 or 12.5.0-02835 or later [16]. Those are the July builds, which the vendor’s September and October advisories both list as affected [1][6]. The Canadian Centre for Cyber Security advisory, updated on 9 October to note exploitation, describes 12.4.3-03670 and 12.5.0-03082 and prior as affected [15]. Those are the vendor’s fixed builds [1]. Both discrepancies are likely transcription errors. Either could cause a build to be marked as compliant or non-compliant incorrectly.
Smaller differences exist elsewhere. The vendor notice carries a publication date of 5 October, most reporting gives 6 October, and Previdian’s timeline places the hotfixes on 7 October [1][2][3][14]. On post-compromise impact, Field Effect’s July account says multifactor seeds were harvested [7], while Volexity’s report confirms directory credential capture and does not mention them [8]. SonicWall’s own September guidance treats them as exposed, instructing token resets alongside password changes [6].
What to do
- Confirm the exact build on every SMA1000 appliance, physical and virtual, against the vendor notice. Accept only 12.4.3-03670 or 12.5.0-03082 or later [1]. Do not rely on a national alert’s version line without checking it against the vendor [15][16].
- Treat any appliance that ran July or September builds while internet-facing as potentially exposed to three exploited or attempted flaws, not one [1][6][7].
- Restrict the Appliance Management Console to trusted administrative networks, and assess whether the Work Place portal needs to be internet-reachable at all [14][17].
- Hunt behaviourally: authentication traffic from the appliance to domain controllers without a matching VPN session, new outbound or lateral connections, unexpected changes to web server routing and startup scripts, and unexpected files or privileged binaries [7][8].
- If compromise is suspected, preserve memory and disk before rebooting, then re-image rather than clean. Rotate every credential that passed through the appliance, including directory service accounts, and reset TOTP tokens [6][8].
The offensive security reading
The useful observation is not that a VPN gateway had another critical flaw. It is that the same class of flaw, in the same interface, recurred three times in twelve weeks, and each fix build became an affected build in the next advisory. For an attacker, a recently closed SSRF in a proxying component is a map of where the next one is likely to be found, and the July and September waves show the interval is short. For a defender, a patch date on an SMA1000 is a statement about the past. One analyst quoted on the October release called the recurrence a pattern rather than bad luck [17]. The practical consequence is narrower: on edge appliances with a recurring flaw class, the compliance record should store the build and the advisory it answers, and exposure of the vulnerable interface should be treated as the control that outlasts the patch cycle.
Sources
Every R3KONX article cites its primary material. 17 sources, in order of first citation. Links open the original publication.
- Product Notice: SMA 1000 Series affected by Multiple Vulnerabilities (SNWLID-2026-0017) SonicWall · 2026-10-05
- CVE-2026-102255 Exploitation Observed: SMA1000 Previdian · 2026-10-12
- Max severity SonicWall SMA1000 flaw now exploited in attacks BleepingComputer · 2026-10-09
- Critical SonicWall Vulnerability Exploited Days After Disclosure SecurityWeek · 2026-10-12
- SonicWall fixes pre-auth SSRF flaw in SMA 1000 appliances (CVE-2026-102255) Help Net Security · 2026-10-07
- Product Notice: SMA 1000 Series affected by Multiple Vulnerabilities (SNWLID-2026-0016) SonicWall · 2026-09-01
- SonicWall SMA1000 zero-days exploited in targeted attacks Field Effect · 2026-07-16
- Proxying to Compromise: SonicWall Secure Mobile Access 0-day Exploitation Volexity · 2026-07-17
- CVE-2026-102255 record National Vulnerability Database, NIST · 2026-10-07
- CVE-2026-83548 record National Vulnerability Database, NIST · 2026-09-01
- CVE-2026-15409 record National Vulnerability Database, NIST · 2026-07-14
- Known Exploited Vulnerabilities Catalog (data feed) CISA, via cisagov/kev-data · 2026-10-08
- CISA: SonicWall SMA1000 flaws now exploited by ransomware gangs BleepingComputer · 2026-08-10
- BSL-A1223: SonicWall SMA1000 CVE-2026-102255 Beazley Security Labs · 2026-10-09
- SonicWall security advisory (AV26-1017) Canadian Centre for Cyber Security · 2026-10-09
- Critical Vulnerability in SonicWall SMA1000 Series (AL-2026-137) Cyber Security Agency of Singapore · 2026-10-08
- SonicWall's latest critical flaw indicates a security pattern, not another one-off bug CSO Online · 2026-10-07
Researched and written by the R3KONX analysis desk from the cited primary material. Two caveats apply. Exploitation of CVE-2026-102255 is reported by honeypot and decoy operators, not by the vendor or in incident response findings, and no successful compromise had been published when this was written. The vendor's PSIRT advisory page did not render retrievable text for this review, so version data is taken from the vendor's product notices, which carry the same advisory identifiers. Corrections to event@r3konx.asia.
