What is CVE-2026-15410?
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.
Timeline
- 2026-07-14Published to the U.S. National Vulnerability Database (NVD)
- 2026-07-14Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
- 2026-07-15First covered in a defend.network daily briefing
- 2026-07-16NVD record last updated
- 2026-07-17CISA federal remediation deadline (BOD 22-01)
CISA Known Exploited Vulnerability
SonicWall SMA1000 Appliances Code Injection Vulnerability
Affected product
SonicWall SMA1000 Appliances
NVD also lists CPE entries for: Sonicwall Sma6210 Firmware, Sonicwall Sma6210, Sonicwall Sma7210 Firmware, Sonicwall Sma7210, Sonicwall Sma8200v
Remediation Steps
- Apply the vendor security update for SonicWall SMA1000 Appliances as a priority.
- Restrict network exposure of the affected service to trusted sources until patched.
- Review logs and detections for indicators of exploitation.
- Confirm fixed versions against the official vendor advisory before deploying.
References
Referenced in our briefings & reports
- Vulnerability Priority Report – Week 2 of August 2026 (August 10 – 16)
- Vulnerability Priority Report – Week 1 of August 2026 (August 3 – 9)
- Vulnerability Priority Report – Week 4 of July 2026 (July 27 – August 2)
- Vulnerability Priority Report – Week 3 of July 2026 (July 20 – 26)
- Vulnerability Priority Report – Week 2 of July 2026 (July 13 – 19)
- WordPress, SonicWall zero-days in active exploitation; FakeGit malware campaign hits 7,600 GitHub repos (2026-07-21)
- Critical zero-days in Microsoft Active Directory, SonicWall SMA1000, GitHub malware campaign (2026-07-15)
Browse all tracked CVEs in the defend.network CVE database →
🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.