/00 — boot sequence

Hello.

Article

CISA Adds SonicWall SMA1000 Zero-Days to KEV: CVE-2026-15409, CVE-2026-15410 Exploited

July 17, 2026•3 min read
sonicwall sma1000 cve-2026-15409 cve-2026-15410 zero-day kev

CISA has added two critical SonicWall SMA1000 vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. The flaws — CVE-2026-15409 (CVSS 9.8) and CVE-2026-15410 (CVSS 9.1) — affect the SMA1000 series SSL VPN appliances and allow unauthenticated remote code execution. If you run SonicWall SMA1000, patch immediately.

What Happened

On July 15, 2026, CISA issued an emergency directive adding two SonicWall SMA1000 CVEs to the KEV catalog with a patch-by date of July 22, 2026 for federal agencies. The vendor released firmware updates on July 14 addressing both flaws.

CVE-2026-15409: Pre-authentication stack-based buffer overflow in the SSL VPN web management interface. An unauthenticated attacker sends a crafted HTTP request to the management port, achieving remote code execution as root. CVSS 9.8.

CVE-2026-15410: Pre-authentication command injection in the same management interface. Improper input sanitization allows an unauthenticated attacker to execute arbitrary system commands. CVSS 9.1.

Both vulnerabilities affect SMA1000 firmware versions 12.4.3-02854 and earlier. The fixed version is 12.4.3-02855 (released July 14, 2026).

Why This Matters

SSL VPN appliances are high-value targets. They sit at the network perimeter, exposed to the internet by design, and provide direct access to internal networks. The SMA1000 series is widely deployed in mid-market and enterprise environments for remote access.

  • No authentication required: Both bugs are pre-auth — attackers don't need credentials
  • Remote code execution: Full device compromise, not just data leak
  • Root privileges: The management interface runs with elevated permissions
  • Actively exploited: CISA doesn't add to KEV on speculation; exploitation is confirmed

This follows a pattern: SonicWall SMA100 (CVE-2021-20016/20017), Fortinet FortiGate (CVE-2022-42475, CVE-2023-27997), Pulse Connect Secure (CVE-2021-22893), Citrix NetScaler (CVE-2023-3519). Perimeter VPN appliances remain a top initial-access vector for ransomware groups and APTs.

Affected Products

ProductAffected VersionsFixed Version
SMA100012.4.3-02854 and earlier12.4.3-02855

Note: The older SMA100 series (CVE-2021-20016/20017) is not affected by these specific CVEs, but should already be patched or replaced.

Mitigation & Patching

  1. Apply firmware 12.4.3-02855 immediately — download from mysonicwall.com
  2. Restrict management interface access — limit to known admin IPs only; never expose to the full internet
  3. Enable MFA for all SSL VPN accounts
  4. Monitor logs for anomalous login attempts, especially from unexpected geolocations
  5. Consider network segmentation — place VPN appliances in a DMZ with strict egress controls

Workaround if immediate patching isn't possible: Block inbound access to the management port (TCP 443 by default) at the firewall level, allowing only designated management subnets. This breaks remote admin but prevents exploitation.

Detection

Watch for these indicators in SMA1000 logs:

  • Repeated failed login attempts to the management interface
  • Unusual HTTP request patterns (oversized headers, malformed parameters)
  • Unexpected outbound connections from the appliance
  • New admin accounts or modified firewall rules

SonicWall provides a detection script on their PSIRT page. CISA also released a Snort rule set (SID 1000456-1000458) for network-based detection.

The Bigger Picture: Perimeter Appliances Under Siege

This is the third major SSL VPN KEV addition in 2026 alone (following FortiGate in March and Citrix in May). The pattern is clear: attackers prefer exploiting edge devices over phishing or credential theft when possible — it's faster, quieter, and bypasses endpoint defenses.

For defenders, the lesson is architectural: reduce the attack surface at the perimeter.

  • Move toward Zero Trust Network Access (ZTNA) / SASE instead of traditional SSL VPN
  • If SSL VPN is required, use vendors with rapid patch cadence and transparent disclosure
  • Automate firmware updates where vendor supports it
  • Enforce strict management-plane isolation

Action Items for This Week

  1. Inventory all SonicWall SMA appliances — confirm model and firmware version
  2. Patch SMA1000 to 12.4.3-02855 before July 22 (CISA deadline)
  3. Verify management interface is not internet-exposed — restrict to admin jump hosts
  4. Run the SonicWall detection script against your environment
  5. Review VPN access logs for the past 30 days for anomalies
  6. Update incident response playbooks to include SMA1000 compromise scenarios

Sources:

  • CISA: "CISA Adds Two SonicWall SMA1000 Vulnerabilities to Known Exploited Vulnerabilities Catalog" (July 15, 2026)
  • SonicWall PSIRT: "Security Advisory SNWLID-2026-0012" (July 14, 2026)
  • The Cyber Express: "CISA Adds SonicWall SMA1000 Vulnerabilities to KEV Catalog Following Active Exploitation" (July 15, 2026)

Automated Transmission

This entry was synthesized and populated dynamically using native API integrations.