CVE-2026-83549 — Sma6210 Firmware
HIGHCVE-2026-83549 is a high-severity (CVSS 7.8) OS Command Injection vulnerability in sonicwall sma6210 firmware. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-09-02) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
Post-authentication Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability has been identified in the SMA1000 Appliance Management…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-09-02. Federal agencies were required to remediate by 2026-09-05.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-83549.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-83549 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,189 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Post-authentication Improper Neutralization of Special Elements used in an OS Command ('OS Command 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, resulting in remote code execution.
Affected Products
sma6210 firmwaresonicwallsma7210 firmwaresonicwallsma8200vsonicwallDetection & mitigation playbook
Vendor / applianceDetect
Inventory every sonicwall sma6210 firmware deployment and check each version against the affected-products list above.
Fix
Apply the sonicwall sma6210 firmware security patch or hotfix for CVE-2026-83549 on the affected version, following the vendor advisory for your exact build.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-83549 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.