CVE-2025-40602
A local privilege escalation vulnerability due to insufficient authorization in the SonicWall SMA1000 appliance management console (AMC).
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable
Can a WAF block it? No. The vulnerability requires local privilege escalation with existing high privileges and does not involve HTTP requests, so a web application firewall cannot detect or block the attack.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-40602 being exploited?
Yes. CVE-2025-40602 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-40602?
CVE-2025-40602 is rated Medium with a CVSS score of 6.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-40602?
Yes. A fix has been recorded for CVE-2025-40602. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-40602 affect?
CVE-2025-40602 affects sonicwall:sma6200_firmware, sonicwall:sma6210_firmware, sonicwall:sma7200_firmware, sonicwall:sma7210_firmware, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected12.4.3-03093 (platform-hotfix) and earlier versions
- affected12.5.0-02002 (platform-hotfix) and earlier versions
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 18 Dec 2025 (SSVC 2.0.3).
timeline
- 17 Dec 2025Added to CISA KEV (exploited in the wild)
- 18 Dec 2025First proof-of-concept repository on GitHub (unvetted) · 1 day later
- 18 Dec 2025Published · same day later
- 18 Dec 2025CISA SSVC assessment: exploitation active · same day later
- 18 Dec 2025CVE record last updated · same day later
- 24 Dec 2025CISA remediation due date (US federal agencies) · 6 days later
- 2 Nov 2026Analysed by vulneraibility.com · 314 days (about 10 months) later
- Advisorypsirt.global.sonicwall.com /vuln-detail/SNWLID-2025-0019
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-40602
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.