SonicWall SonicOS improper access control exploited by Akira
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Active exploitation of SonicWall firewall management and SSLVPN access control flaw linked to Akira ransomware campaigns targeting Gen 7 devices.
A critical improper access control vulnerability in SonicWall SonicOS management access and SSLVPN (CVE-2024-40766) is being actively exploited in the wild. SonicWall reports the vulnerability affects SOHO Gen 5 (5.9.2.14-12o and older), Gen 6 (6.5.4.14-109n and older), and Gen 7 firewalls (7.0.1-5035 and older). Recent 2025 threat activity has documented targeted attacks against Gen 7 SonicWall firewalls with SSLVPN enabled, directly linked to Akira ransomware campaigns. Attackers have exploited migrated local accounts with unchanged passwords to gain initial access to affected firewalls. Successful exploitation allows unauthorized resource access and administrative privileges, potentially enabling attackers to view, change, or delete data and cause denial of service by crashing the firewall.
Defenders must immediately patch to SonicWall firmware 7.3.0 or later for Gen 7 devices, reset all local SSLVPN user account passwords—particularly those migrated from Gen 6 to Gen 7—enforce multi-factor authentication, and remove unused accounts. The vulnerability exploits improper access control in a public-facing application surface and serves as an initial access vector for ransomware deployment. Organizations running affected SonicWall generations should prioritize patching and credential hygiene to prevent ransomware intrusion.
Mentioned in this report
Source reporting: https://www.cisecurity.org/advisory/a-vulnerability-in-sonicwall-sonicos-management-access-and-sslvpn-could-allow-for-unauthorized-access_2024-097
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs