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.
CVE-2026-15409
“—” beside the score: it is equal to the CVSS score beside it.
Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-07-14), indicating real-world exploitation has been confirmed by US federal agencies. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 10.0 retained for reference (NVD's own analysis pending). Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (SonicWall, Inc.) lists SonicWall SMA1000 versions 12.4.3-03245 up to and including 12.4.3-03434 and 12.5.0-02283 up to and including 12.5.0-02800 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALhigh confidence
- EG Risk
- 100EG Risk 100/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity100% × 45%The EG Score, 10.0 of 10.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix. - EPSS PROB
- 6.8%
- EPSS %ILE
- 93rd
- KEV
- ⚠ Exploited
SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.
In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0008 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-15409
Published
July 14, 2026
Last Modified
August 4, 2026
Advisory Details (2)
Auto-updated Oct 13, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-15409Vendor Advisories for CVE-2026-15409(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 50× in last 7d / 241× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 707 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 607 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-14 11:13 UTCEG score recompute
- 2026-10-14 11:12 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-13 08:50 UTCEG score recompute
- 2026-10-13 08:50 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-12 16:32 UTCEG score recompute
- 2026-10-12 06:29 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 02:45 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 23:02 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 19:21 UTCEG score recompute
- 2026-10-11 19:21 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 17:22 UTCEG score recompute
- 2026-10-11 15:39 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 14:55 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-11 11:57 UTCEG score recompute
- 2026-10-11 11:57 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 08:15 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 04:33 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 00:51 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 21:08 UTCEG score recompute
- 2026-10-10 21:07 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-10 17:25 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
Show 75 moreShow fewer
- 2026-10-10 13:43 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 10:01 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 06:20 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 02:38 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 22:57 UTCEG score recompute
- 2026-10-09 22:57 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-09 19:15 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 15:33 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 11:51 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 08:07 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 04:26 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 00:44 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 21:02 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 17:21 UTCEG score recompute
- 2026-10-08 17:20 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-08 13:38 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 09:54 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 06:13 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 02:30 UTCEG score recompute
- 2026-10-08 02:30 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-07 22:48 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 19:05 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 15:24 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 11:42 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 07:59 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 04:18 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 00:36 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 20:53 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 17:10 UTCEG score recompute
- 2026-10-06 17:10 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-06 13:29 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 09:48 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 02:14 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 22:31 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 18:50 UTCEG score recompute
- 2026-10-05 18:50 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-05 15:08 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 11:26 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 07:44 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 04:01 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 00:20 UTCEG score recompute
- 2026-10-05 00:20 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-04 20:36 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-04 16:54 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-04 13:11 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-04 09:29 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-04 05:48 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-04 02:06 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 22:24 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 18:41 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 14:59 UTCEG score recompute
- 2026-10-03 14:58 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-03 11:16 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 07:33 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 03:49 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-03 00:07 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-02 20:25 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-02 16:43 UTCEG score recompute
- 2026-10-02 16:43 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-02 13:01 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-02 09:20 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-02 05:38 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-02 01:56 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-01 22:15 UTCEG score recompute
- 2026-10-01 22:14 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 6.8% · 93rd percentile
- 2026-10-01 18:32 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-01 14:50 UTCGHSA enrichmentGHSA-35rc-2vcv-r6q5 · GitHub severity CRITICAL · GitHub CVSS 10.0
Publicly available exploits
(6 references)Public exploit code is referenced for this CVE (1 Metasploit module, 4 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.
- Metasploitexploit/linux/http/sonicwall_sma1000_wsproxy_rce✓ verifiedPublished Aug 10, 2026
SonicWall SMA1000 WorkPlace wsproxy SSRF Remote Command Execution
Open source ↗ - GitHub PoCCh4120N/CVE-2026-15409Published Aug 3, 2026
Proof-of-Concept exploit for CVE-2026-15409 (SonicWall SMA 1000 RCE) via Erlang distribution over WebSocket. Achieves unauthenticated remote code execution as couchdb user.
Open source ↗ - Nucleijavascript/cves/2026/CVE-2026-15409.yamlPublished Jul 21, 2026
SonicWall SMA1000 - Server-Side Request Forgery
Open source ↗ - GitHub PoCtc4dy/CVE-2026-15409-15410-FrameworkPublished Jul 17, 2026
CVE-2026-15409/15410 SonicWall SMA1000 multi-exploit Framework 🔥 SSRF→Erlang RPC→RCE→root privesc. Features: --detect safe check, --exec, --read-file, --privesc, --rpc, interactive shell, batch threading, file write, ws-url override, pipe support.🛡️ KEV listed CVSS 10.0 actively exploited. Authorized testing only. Use Ethically, Stay Legal. 🔒
Open source ↗ - GitHub PoC0xBlackash/CVE-2026-15409Published Jul 15, 2026
CVE-2026-15409
Open source ↗ - GitHub PoCremmons-r7/rapid7-CVE-2026-15409Published Jul 15, 2026
This repo contains a proof-of-concept exploit for CVE-2026-15409. It establishes non-root remote code execution on SonicWall SMA 1000 by implementing the Erlang protocol expected by localhost:1050 and tunneling it through the websocket for file r/w and arbitrary code execution via RPC calls.
Open source ↗
Related CVEs(same CWE)
Frequently asked(6)
What is CVE-2026-15409?
When was CVE-2026-15409 made public?
Is CVE-2026-15409 actively exploited?
What is the CVSS score of CVE-2026-15409?
Which products are affected by CVE-2026-15409?
How do I remediate CVE-2026-15409?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15409
Is Your Infrastructure Affected by CVE-2026-15409?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.