CVE-2026-15410

CRITICALPre-NVD 7.29.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score elevated to 9.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 7.2 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 12%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

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.

Post-authentication improper control of generation of code ('Code Injection') vulnerability has been identified in the SMA1000 Appliance Management Console (AMC) which in specific conditions could potentially enable a remote authenticated attacker as administrator to execute arbitrary OS commands.

CVSS v3
7.2
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/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)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (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 within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact, and watch the vendor's advisory for the fix.
EPSS PROB
12%
EPSS %ILE
96th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable no (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; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (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-15410

Published

July 14, 2026

Last Modified

August 4, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet.
CISA🔴 Active Exploitation

Known 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-15410

Vendor Advisories for CVE-2026-15410(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 47× in last 7d / 228× 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 99 of 675 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 576 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:13 UTCEG score recompute
  2. 2026-10-14 01:13 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 12% · 96th percentile
  4. 2026-10-13 03:35 UTCEG score recompute
  5. 2026-10-13 03:35 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 12% · 95th percentile
  7. 2026-10-12 16:32 UTCEG score recompute
  8. 2026-10-12 05:54 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  9. 2026-10-12 01:48 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  10. 2026-10-11 21:45 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  11. 2026-10-11 20:10 UTCEG score recompute
  12. 2026-10-11 17:40 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  13. 2026-10-11 17:22 UTCEG score recompute
  14. 2026-10-11 14:55 UTCEG score recompute
  15. 2026-10-11 13:48 UTCEPSS rescoreEPSS 12% · 95th percentile
  16. 2026-10-11 13:35 UTCEG score recompute
  17. 2026-10-11 13:34 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  18. 2026-10-11 09:30 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  19. 2026-10-11 05:26 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  20. 2026-10-11 01:23 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  21. 2026-10-10 21:20 UTCEG score recompute
  22. 2026-10-10 21:19 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  23. 2026-10-10 19:59 UTCEPSS rescoreEPSS 12% · 95th percentile
  24. 2026-10-10 17:14 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  25. 2026-10-10 13:10 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
Show 74 more
  1. 2026-10-10 09:06 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  2. 2026-10-10 05:03 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  3. 2026-10-10 01:00 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  4. 2026-10-09 20:56 UTCEG score recompute
  5. 2026-10-09 20:56 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 12% · 95th percentile
  7. 2026-10-09 16:52 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  8. 2026-10-09 12:49 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  9. 2026-10-09 08:45 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  10. 2026-10-09 04:41 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  11. 2026-10-09 00:38 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  12. 2026-10-08 20:35 UTCEG score recompute
  13. 2026-10-08 20:35 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  14. 2026-10-08 17:11 UTCEPSS rescoreEPSS 12% · 95th percentile
  15. 2026-10-08 16:32 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  16. 2026-10-08 12:27 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  17. 2026-10-08 08:24 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  18. 2026-10-08 04:21 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  19. 2026-10-08 00:17 UTCEG score recompute
  20. 2026-10-08 00:17 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  21. 2026-10-07 23:47 UTCEPSS rescoreEPSS 12% · 95th percentile
  22. 2026-10-07 20:14 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  23. 2026-10-07 16:10 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  24. 2026-10-07 12:06 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  25. 2026-10-07 08:01 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  26. 2026-10-07 03:57 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  27. 2026-10-06 23:54 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  28. 2026-10-06 19:50 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  29. 2026-10-06 15:47 UTCEG score recompute
  30. 2026-10-06 15:47 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  31. 2026-10-06 15:17 UTCEPSS rescoreEPSS 12% · 95th percentile
  32. 2026-10-06 11:44 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  33. 2026-10-06 07:41 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  34. 2026-10-06 03:38 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  35. 2026-10-05 23:35 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  36. 2026-10-05 19:30 UTCEG score recompute
  37. 2026-10-05 19:30 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  38. 2026-10-05 17:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  39. 2026-10-05 15:26 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  40. 2026-10-05 11:21 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  41. 2026-10-05 07:18 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  42. 2026-10-05 03:14 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  43. 2026-10-04 23:11 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  44. 2026-10-04 19:08 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  45. 2026-10-04 15:04 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  46. 2026-10-04 11:00 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  47. 2026-10-04 06:57 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  48. 2026-10-04 02:53 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  49. 2026-10-03 22:50 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  50. 2026-10-03 18:46 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  51. 2026-10-03 14:43 UTCEG score recompute
  52. 2026-10-03 14:43 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  53. 2026-10-03 14:25 UTCEPSS rescoreEPSS 12% · 95th percentile
  54. 2026-10-03 10:38 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  55. 2026-10-03 06:34 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  56. 2026-10-03 02:30 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  57. 2026-10-02 22:27 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  58. 2026-10-02 18:24 UTCEG score recompute
  59. 2026-10-02 18:24 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  60. 2026-10-02 14:21 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  61. 2026-10-02 10:16 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  62. 2026-10-02 06:13 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  63. 2026-10-02 02:09 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  64. 2026-10-01 22:04 UTCEG score recompute
  65. 2026-10-01 22:03 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  66. 2026-10-01 19:49 UTCEPSS rescoreEPSS 12% · 95th percentile
  67. 2026-10-01 17:57 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  68. 2026-10-01 13:51 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  69. 2026-10-01 09:48 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  70. 2026-10-01 05:45 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  71. 2026-10-01 01:42 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  72. 2026-09-30 21:39 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2
  73. 2026-09-30 17:36 UTCEG score recompute
  74. 2026-09-30 17:36 UTCGHSA enrichmentGHSA-pxc4-295p-35qq · GitHub severity HIGH · GitHub CVSS 7.2

Frequently asked(6)

What is CVE-2026-15410?
CVE-2026-15410 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Post-authentication improper control of generation of code ('Code Injection') vulnerability has been identified in the SMA1000 Appliance Management Console (AMC) which in specific conditions could potentially enable a remote authenticated attacker as administrator to execute arbitrary OS commands.
When was CVE-2026-15410 made public?
CVE-2026-15410 was made public on July 14, 2026: that is the date its CVE record's CNA, SonicWall, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of August 4, 2026; the record at its source may have been updated since.
Is CVE-2026-15410 actively exploited?
Yes. CISA added CVE-2026-15410 to the Known Exploited Vulnerabilities catalog on July 14, 2026, affecting SonicWall SMA1000 Appliances. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2026-15410?
CVE-2026-15410 has a CVSS v3.1 base score of 7.2 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2026-15410?
CVE-2026-15410 affects SonicWall SMA1000 Appliances.
How do I remediate CVE-2026-15410?
No fix for CVE-2026-15410 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory 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. The vendor advisories EchelonGraph has for CVE-2026-15410 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15410

Explore →

Is Your Infrastructure Affected by CVE-2026-15410?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.