SonicWall SMA1000 Appliances Server-Side Request Forgery Vulnerability (CVE-2026-15409)
Published Last modified In CISA KEV since Sources: NCSC NZ, CVE.org, BSI, pwn.watch, SingCERT
- Actively exploited
- Source: VulnCheck KEV (opens in a new tab), CERT.at, ANSSI / CERT-FR, CSA/SingCERT How we classify
- Ransomware
- Public exploit
What is affected, what to do
A Server-Side Request Forgery (SSRF) vulnerability in SonicWall SMA1000 Appliances allows an unauthenticated remote attacker to make the appliance send requests to unintended locations. This affects the SMA6210 and SMA7210 firmware versions. The vulnerability is actively exploited in ransomware campaigns and can be executed remotely without authentication. Immediate patching to the latest firmware version is critical to mitigate this risk.
The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update SMA 1000 Models-6210, 7210, 8200v to version 12.4.3-03453. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- SonicWall SMA1000
lte 12.4.3-03245..12.4.3-03434 - SonicWall SMA1000
lte 12.5.0-02283..12.5.0-02800
- SonicWall SMA1000
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
10.0
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
10.0
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: NCSC NZ, CVE.org, BSI, pwn.watch, SingCERT
6.8 %
EPSS score
Moderate — model estimates 1-10% exploitation likelihood.
Source: FIRST EPSS, percentile 94.0
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 266.70 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab), CERT.at, ANSSI / CERT-FR, CSA/SingCERT How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 10.0 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 10.0
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 6.8 %
- Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 94.0
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossaryCWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-918
Response and mitigation
Why act now?
Prioritisation rationale
This flaw is network-reachable with no authentication and no user interaction. The scope change means an attacker can turn the appliance into a pivot into internal networks and trusted backend services, with maximum impact on confidentiality, integrity and availability. CISA flags known use in ransomware campaigns, and SMA gateways are a favoured initial-access vector for ransomware operators who mass-scan remote-access products before moving laterally into AD. Exploitation likelihood is very high relative to the overall CVE population. Treat any internet-facing affected SMA1000 as critical and patch within 24 hours; internal-only instances can follow, but within days rather than weeks.
Runbook step 1
Immediate response (0-24 h)
- Inventory: Identify every SonicWall SMA1000 appliance (including SMA 6210) and check its firmware. Affected builds are 12.4.3-03245 through 12.4.3-03434 and 12.5.0-02283 through 12.5.0-02800 (including 12.4.3-03387 and 12.5.0-02624).
- Patch: A patch is available from the vendor. Look up the fixed build in the SonicWall PSIRT advisory and push it as an emergency change outside the normal maintenance window.
- Cut exposure if you cannot patch now: Restrict the Work Place interface (HTTPS/443) at the perimeter firewall to known source ranges (partners, geo-fencing), or temporarily front it with an authenticating reverse proxy. The Appliance Management Console must never be reachable from the internet.
- Preserve evidence first: Export appliance logs and configuration (or take a forensic snapshot) before upgrading, because the update may overwrite traces. Patch only after that.
- Rotate secrets: If you see any sign of SSRF abuse, rotate LDAP/AD bind accounts, RADIUS shared secrets, local admin accounts and any service credentials reachable from the appliance. Terminate active VPN sessions.
- Regulatory clock: If you suspect successful exploitation, start the NIS2 24-hour early-warning track with your national CSIRT/authority and activate IR.
Runbook step 2
Mitigation layers
- Network egress filtering: Firewall the appliance's outbound traffic down to what it genuinely needs: auth servers, DNS, NTP and defined backend applications. Explicitly deny management networks, hypervisor consoles, cloud metadata endpoints (169.254.169.254) and loopback-adjacent services. This is the single most effective SSRF control.
- DMZ architecture: Host the appliance in a dedicated DMZ. Allow DMZ-to-internal traffic only via a destination IP plus port allowlist, with no "any" rules towards server VLANs.
- WAF/IPS: In front of Work Place, block requests whose parameters, headers or paths carry URLs or IPs, especially
http://127.,localhost,169.254., RFC1918 ranges,file://,gopher://and URL-encoded or decimal/hex IP obfuscations. Update Suricata/Snort or vendor IPS feeds for CVE-2026-15409 signatures. - IAM/least privilege: Reduce the appliance's directory service accounts to read-only and enforce MFA for all Work Place users and admins. SSRF abuses the appliance's trusted backend relationships, so limit what that trust is worth.
- Configuration hardening: Remove unused portals, resource definitions and bookmarks. Restrict management access to a dedicated admin network or jump host.
Runbook step 3
Detection rules
- Appliance access logs (syslog to SIEM): Hunt for unauthenticated Work Place requests carrying URL-like parameter values. SPL sketch:
index=sonicwall sourcetype=sma* (uri_query="*http*" OR uri_query="*127.0.0.1*" OR uri_query="*169.254*" OR uri_query="*localhost*") user="-" - Network telemetry (Zeek/Suricata/firewall): Look for new or rare connections from the appliance IP to internal destinations outside the known backend allowlist, especially management ports (22, internal 443/8443, 5985/5986, 3389), metadata endpoints or loopback services. KQL sketch:
CommonSecurityLog | where SourceIP == "<SMA-IP>" and DestinationIP !in (allowlist) | summarize count() by DestinationIP, DestinationPort - DNS logs: Appliance lookups of unfamiliar external domains, especially OAST/callback services such as
*.oast.*,*.interact.shor*.burpcollaborator.net, are classic SSRF probing. - Downstream activity: Watch for Windows Event IDs 4624/4625 (logon type 3) and 4776 sourced from the appliance IP at odd hours or for unusual accounts. Also flag VPN sessions from new source IPs that closely follow suspicious Work Place requests.
- Sigma shape:
logsource: firewall | selection: src_ip: <SMA-IP>, dst_ip|cidr: [10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16] | filter: dst_ip in allowlist | condition: selection and not filter
- Appliance access logs (syslog to SIEM): Hunt for unauthenticated Work Place requests carrying URL-like parameter values. SPL sketch:
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000 Appliance Work Place interface. A remote unauthenticated attacker could potentially cause the appliance to make requests to unintended location.
Source: NCSC NZ (CC BY 4.0), NVD (NIST), CISA KEV Catalog, cvelistv5, BSI CSAF, BSI WID Portal, pwn.watch, CSA/SingCERT
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| SonicWall | SMA1000 |
|
|
| sonicwall | sma8200v |
|
|
| SonicWall | SMA 1000 Models-6210, 7210, 8200v |
|
|
Vendors and products
Affected operating systems
| Other | sonicwall | sma6210_firmware | 12.4.3-03245 |
| Other | sonicwall | sma6210_firmware | 12.4.3-03387 |
| Other | sonicwall | sma6210_firmware | 12.4.3-03434 |
| Other | sonicwall | sma6210_firmware | 12.5.0-02283 |
| Other | sonicwall | sma6210_firmware | 12.5.0-02624 |
| Other | sonicwall | sma6210_firmware | 12.5.0-02800 |
| Other | sonicwall | sma7210_firmware | 12.4.3-03245 |
| Other | sonicwall | sma7210_firmware | 12.4.3-03387 |
| Other | sonicwall | sma7210_firmware | 12.4.3-03434 |
| Other | sonicwall | sma7210_firmware | 12.5.0-02283 |
| Other | sonicwall | sma7210_firmware | 12.5.0-02624 |
| Other | sonicwall | sma7210_firmware | 12.5.0-02800 |
Weakness classes (CWE)
CWE-918Server-Side Request Forgery (SSRF)
Base
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Entry at MITRE CWE-918
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited | |
| CSA/SingCERT | Multiple Vulnerabilities in SonicWall SMA1000 Series (opens in a new tab)CSA/SingCERT | actively exploited | |
| ANSSI / CERT-FRLicence Ouverte 2.0, as of | CERTFR-2026-ALE-006 – Multiples vulnérabilités dans Sonicwall Secure Mobile Access (clôturée 2026-08-24) (opens in a new tab)cert.cyber.gouv.fr | actively exploited | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-15409 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-15409-PoC-Exploit (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | SonicWall-SMA1000-Zero-Day-IoC-Check (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-15409 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | rapid7-CVE-2026-15409 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-15409 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified |
References & sources
- psirt.global.sonicwall.comSonicWall SMA1000 Appliances — CVE-2026-15409Vendor advisory, pwn-watch, Vendor advisory
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-15409government-resource, US government resource
- cert.atCERT.at: Kritische Sicherheitslücken in SonicWall SMA1000 Series - aktiv ausgenutzt - Updates verfügbarcert-at
- cert.cyber.gouv.frANSSI / CERT-FR: CERTFR-2026-ALE-006 – Multiples vulnérabilités dans Sonicwall Secure Mobile Access (clôturée 2026-08-24)cert-fr
- pwn.watchpwn.watch: SonicWall SMA1000 Appliances: SonicWall SMA1000 Appliances Server-Side Request Forgery Vulnerabilitypwn-watch
- NVD (NIST)NVD: CVE-2026-15409pwn-watch
- NVD (NIST)NVD: CVE-2026-15410pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
One NVD translation into another language is hidden.
Linked advisories
- SonicWall’s latest critical flaw indicates a security pattern, not another one-off bugCSO Online
- Progress Kemp LoadMaster Flaw Exploited; SonicWall SMA1000 Flaws Exploited in RansomwareSANS NewsBites
- @RISK®: The Consensus Security Vulnerability Alert: Vol. 26, Num. 28SANS @RISK
- Patch SonicWall SMA1000 Models for Two Flaws, One Max-SeveritySANS NewsBites
- @RISK®: The Consensus Security Vulnerability Alert: Vol. 26, Num. 27SANS @RISK
- Multiples vulnérabilités dans Sonicwall Secure Mobile Access (15 juillet 2026)CERT-FR (ANSSI)
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-15409"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-15409.svg?lang=en" alt="CVE-2026-15409 – NEOSEC Intel" height="20"></a>