IRONSMITHINTEL
MEDIUMCVSS6.6
|
Actively Exploited
|CISA KEV|CVE-2025-40602|Auth: high — administrative privileges|Reboot: required|Manual only

SonicWall SMA1000 Missing Authorization Vulnerability (CVE-2025-40602)

SonicWall SMA1000 contains a missing authorization vulnerability that could allow for privilege escalation appliance management console (AMC) of affected devices.

Published Dec 18, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, with administrative privileges, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-12-24 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-250) (CWE-250) vulnerability in SonicWall SMA1000 appliance. A local privilege escalation vulnerability due to insufficient authorization in the SonicWall SMA1000 appliance management console (AMC). Exploitation requires remote network access, higher attack complexity, an administrative account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●IT Security
●Running sma6200 firmware: v < 12.4.3-03245, 12.5.0 ≤ v < 12.5.0-02283; sma6210 firmware: v < 12.4.3-03245, 12.5.0 ≤ v < 12.5.0-02283; sma7200 firmware: v < 12.4.3-03245, 12.5.0 ≤ v < 12.5.0-02283; sma7210 firmware: v < 12.4.3-03245, 12.5.0 ≤ v < 12.5.0-02283; sma8200v: v < 12.4.3-03245, 12.5.0 ≤ v < 12.5.0-02283
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-12-17 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-12-24.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2025-40602's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2025-40602↗ MSRC Advisory↗ NVD↗ Vendor Advisory