CVE-2025-23006
Pre-authentication deserialization of untrusted data vulnerability has been identified in the SMA1000 Appliance Management Console (AMC) and Central Management Console (CMC), which in specific conditions could potentially enable a remote unauthenticated attacker to execute arbitrary OS commands.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.
Also consider: allow-list classes · patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-23006 being exploited?
Yes. CVE-2025-23006 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-23006?
CVE-2025-23006 is rated Critical with a CVSS score of 9.8. 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-23006?
Yes. A fix has been recorded for CVE-2025-23006. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-23006 affect?
CVE-2025-23006 affects sonicwall:sma8200v, sonicwall:sma6200_firmware, sonicwall:sma6210_firmware, sonicwall:sma7200_firmware, and 4 further products or versions. 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-02804 (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.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 23 Jan 2025 (SSVC 2.0.3).
timeline
- 23 Jan 2025CISA SSVC assessment: exploitation active
- 23 Jan 2025Published · 1 day later
- 24 Jan 2025Added to CISA KEV (exploited in the wild) · same day later
- 14 Feb 2025CISA remediation due date (US federal agencies) · 21 days later
- 4 Aug 2026CVE record last updated · 536 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 91 days (about 3 months) later
- Advisorypsirt.global.sonicwall.com /vuln-detail/SNWLID-2025-0002
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-23006
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
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.