Press TechRound interviews Secure.com CEO on the future of AI security
Read

Attackers Are Chaining Two SonicWall VPN Zero-Days to Break Into Corporate Networks

Two SonicWall SMA 1000 VPN zero-days are being chained for remote code execution. Here is what happened, who is affected, and what to do now.

Dateline: September 2, 2026

TL;DR: The box that lets your remote workers in is now the box letting attackers in. SonicWall confirmed on Tuesday that two previously unknown flaws in its SMA 1000 remote access appliances are being exploited right now. Chained together, they hand an attacker code execution on the device with no username or password required. These gateways sit at the edge of enterprise, government, and managed service provider networks, which makes them a prized target and a quiet one.

What Happened?

SonicWall’s own security team found the two flaws and, more alarming, found evidence they were already being used. The vendor pushed an emergency hotfix and urged everyone to apply it immediately.

Here is how the pair works together.

The first flaw, tracked as CVE-2026-83548, is a pre-authentication server-side request forgery bug in the Appliance Work Place interface. It carries a maximum severity score of 10.0. A remote attacker with no credentials can abuse it to reach sensitive functions they should never touch.

The second flaw, CVE-2026-83549, scored 7.8, is an OS command injection bug in the Appliance Management Console. On its own it needs admin access. But chain it behind the first flaw, and an unauthenticated attacker can run arbitrary commands on the appliance. That is full takeover from the open internet.

The flaws affect the SMA 1000 models 6210, 7210, and 8200v, both physical and virtual. They do not touch the SMA 100 line or SonicWall firewalls.

What’s the Impact?

A VPN gateway is not just another server. It is the front door for remote staff, and it usually holds a trusted position deep inside the network. Compromise one and an attacker skips past the perimeter entirely, landing somewhere most defenses assume is already safe.

The worse part is visibility. Edge appliances often run with thin logging and little monitoring, so an intruder can sit quietly and dig in for weeks before anyone notices. This is not a one-off for SonicWall either. The same SMA 1000 line was hit by zero-days in July, and those earlier bugs were later picked up by ransomware crews. When a product gets targeted this repeatedly, treating each new advisory as urgent is the only safe assumption.

One catch for defenders: SonicWall has not published any indicators of compromise, and the flaws are not yet in the CISA catalog. That does not mean you are clear. It means you have to hunt for behavior, not signatures.

SMA 1000 zero-days Detection and response

No traditional IOCs published yet. Hunt behavior and check versions.

!Vulnerable versions
12.4.3-03453 and older
12.5.0-02835 and older

Models 6210, 7210, 8200v. SMA 100 and firewalls not affected.

Fixed versions
12.4.3-03526
12.5.0-02952

Apply the hotfix now. Anything below these stays exposed.

👁Behaviors to hunt
  • Unexpected outbound requests from the appliance (SSRF)
  • New processes or shell commands from the console
  • Admin logins or config changes you cannot account for
  • Edge device with little logging going quiet or odd
If compromise is found
  • Re-image hardware or re-deploy virtual appliances
  • Reset all user and administrator passwords
  • Regenerate TOTP tokens
  • Contact SonicWall support to review for compromise
i Not yet in the CISA KEV catalog. Treat as actively exploited regardless.

How to Avoid This

  • Apply the hotfix now. Fixed builds are 12.4.3-03526 and 12.5.0-02952. Anything older stays open.
  • Hunt for behavioral signs: odd outbound requests from the appliance, unexplained admin logins, new processes, or config changes you cannot account for.
  • If you find a compromise, re-image the hardware or re-deploy virtual appliances. Do not just patch over it.
  • Reset every user and admin password, and regenerate TOTP tokens.
  • Limit who can reach the management interface. A VPN gateway does not need its admin console open to the whole internet.