Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Jul 2026.
Sma6210 FirmwareOperating system · Sonicwall
CVE-2026-15410
HIGH · 7.2 CVSS v3.1Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists.There is no fixed release. A documented workaround reduces exposure in the meantime.
In the wildHigh EPSSRemotely reachableZero-click5 weeks old
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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.
In the news
Third-party coverage
Trending covered by 3 outlets this week · latest 4w ago
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence
A post-authentication code injection vulnerability exists in the SMA1000 Appliance Management Console (AMC) where an authenticated administrator user can execute arbitrary OS commands due to improper control of code generation. The attacker must have valid administrator credentials to exploit this vulnerability.
MitigationRestrict administrative access toAMC using network segmentation and strong credential policies. Apply vendor patches when available and monitor for unauthorized administrative sessions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Identify the SMA100 appliance model
Access the Appliance Management Console or check the device label to determine if the model is Sma6210, Sma7210, or Sma8200v
Affected if The device is not one of these three models, as only these are affected by this CVE
Check the installed firmware version
Log into the SMA100 Management Console and navigate to System > Status or use the 'version' command via CLI to retrieve the current firmware version
Affected if The firmware version matches exactly one of: 12.4.3-03245, 12.4.3-03387, 12.4.3-03434, 12.5.0-02283, 12.5.0-02624, or 12.5.0-02800 - only these exact versions are vulnerable
Confirm the Appliance Management Console (AMC) is enabled
Access the SMA100 admin interface and verify if the Appliance Management Console feature is accessible or enabled under the management settings
Affected if AMC is not enabled or accessible - the vulnerability requires AMC to be available for the attack surface to exist
Audit administrative accounts
Review the list of configured administrator accounts in the SMA100 user management section
Affected if Multiple admin accounts exist - the vulnerability requires an authenticated administrator session to exploit, so any valid admin credential could be used as an attack vector
Search for anomalous command execution logs
Review system logs, audit logs, and command history in the AMC or syslog exports for unexpected or unauthorized OS commands, particularly those originating from the web interface
Affected if Unfamiliar commands or commands executed outside of normal administrative activities are found in the logs
A user is affected if they are running any of the exact firmware versions listed (12.4.3-03245, 12.4.3-03387, 12.4.3-03434, 12.5.0-02283, 12.5.0-02624, or 12.5.0-02800) on an Sma6210, Sma7210, or Sma8200v appliance with AMC enabled and accessible to authenticated administrators.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data
Mitigation availableNo clean upgrade yet — mitigate in the meantime
Mitigation
Restrict administrative access toAMC using network segmentation and strong credential policies. Apply vendor patches when available and monitor for unauthorized administrative sessions.
Fix this in Sma6210 Firmware
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-15410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 92%6 agents6 Aug 2026
CVE-2026-15410 in SonicWall SMA1000's AMC (Advanced Management Console) is classified as post-authentication, but treat that label with skepticism. A 0.76 EPSS score paired with KEV status is anomalous for post-auth vulnerabilities — EPSS this high typically correlates with pre-auth or wormable flaws. The fact that this one sits here anyway signals that the 'authentication barrier' is thinner than the classification suggests. Management consoles like AMC are routinely exposed to the internet for admin convenience, often use weak or shared credentials, and receive far less security monitoring than production workloads. Attackers compromising those credentials don't need an auth bypass — they've already walked through the front door. Once inside AMC, they have hub-and-spoke control over your entire SMA1000 fleet. That's not a single-appliance compromise; it's an administrative backdoor to everything that appliance manages.
The 'specific conditions' qualifier in the advisory is a red flag for a different reason: it signals that SonicWall has not fully characterized the attack surface. When vendors use vague scope-limiting language, defenders cannot assess whether they're actually in the blast radius. Assume you might be until proven otherwise — optimistic assumptions are where incidents begin.
What you should do: verify whether your AMC interface is internet-facing and if so, treat it as a high-priority exposure. Audit your AMC logs for administrator-level command execution with the same fidelity you'd apply to production service monitoring — most SMA1000 deployments likely don't, and that's exactly where exploitation slips through. Check your AMC firmware version against SonicWall's patch history for this product line; CVE-2022-22290 and CVE-2021-20024 show a pattern of similar post-auth flaws in the same management plane. Finally, when patching, verify whether the update includes session token rotation — applying the fix doesn't automatically revoke an attacker's existing admin session if they've already compromised credentials.
Peer-ranked notes from engineers who’ve handled CVE-2026-15410 in production — separate from our analysis above.
Know something about CVE-2026-15410?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
▲0
The WardenAI discussion synthesisdbcve analysis2026-08-04
AI analysis
CVE-2026-15410 carries a dangerous contradiction: it's classified as post-authentication yet holds a 0.76 EPSS score and KEV status. This combination should not happen. High EPSS scores typically correlate with pre-authentication vulnerabilities, wormable flaws, or exposures in massively-deployed software. Post-auth vulns rarely cross the 0.75 threshold because the authentication barrier is supposed to be the mitigating control.
If this vulnerability is being actively exploited in the wild, treat the 'post-authentication' label as a question, not an answer. Ask instead: how are attackers becoming administrators on these SonicWall SMA100 appliances?
The likely explanations are concerning. Either the AMC (Access Management Console) authentication is routinely bypassed through credential theft, session hijacking, or phishing — or this vulnerability is being chained with an initial compromise to achieve admin-level access. Either way, 'administrator required' is not your shield.
The vague 'specific conditions' qualifier in the advisory is a red flag. When vendors leave attack preconditions unspecified, it typically means the full attack surface hasn't been characterized internally. You cannot properly assess your risk if you don't know what those conditions are.
What to do now: determine whether your AMC interface is internet-facing and, if so, treat it as a critical exposure. Review your logging to ensure admin-level command execution within AMC is captured with sufficient fidelity to detect exploitation attempts. Assume the 'specific conditions' could apply to your environment until proven otherwise.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data