Knox CVE Database
/
CVE-2026-83549
High
7.8

CVE-2026-83549: SonicWall SMA1000 Appliances OS Command Injection Vulnerability

SonicWall SMA1000 Appliances contains an OS command injection vulnerability that could enable a remote authenticated attacker as administrator to execute arbitrary OS commands, resulting in remote code execution.

Added to the CISA KEV catalog:
September 2, 2026

Overview

SonicWall SMA1000 appliances running firmware versions 12.4.3-03453 and older, or 12.5.0-02835 and older, contain an OS command injection flaw in the Appliance Management Console (AMC). An attacker with administrator credentials can submit crafted input containing shell metacharacters to the AMC, causing the appliance to execute arbitrary operating system commands and achieving remote code execution. SonicWall PSIRT has confirmed active exploitation of this vulnerability in the wild.

Vulnerability details

Affected vendor
SonicWall
Affected product
SMA1000 Appliances
Weakness type (CWE)
CWE-78

The AMC in affected SMA1000 firmware fails to sanitize attacker-controlled input before passing it to an OS command interpreter, a classic CWE-78 condition. When an application constructs shell commands by concatenating user-supplied strings without stripping or escaping metacharacters such as semicolons, pipes, or backticks, an attacker can break out of the intended command context and inject arbitrary instructions. The AMC is the administrative management interface for the appliance, meaning the injection point sits within a privileged management plane rather than a general user-facing surface.


An attacker who holds administrator-level credentials to the AMC submits crafted input containing OS command injection payloads to the interface. The appliance processes the input without adequate neutralization and executes the injected commands with the privileges of the process running the AMC. The result is arbitrary code execution on the underlying operating system. The vendor advisory notes that specific, unspecified conditions must be met for the flaw to be triggerable, and SonicWall PSIRT has confirmed at least one case of active exploitation, making this a high-priority remediation target.

Severity and impact

7.8
High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Exploitation status

This vulnerability is confirmed as actively exploited in the wild — it is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

Known ransomware campaign use
Unknown

Detection and monitoring

  • Review AMC audit logs for administrator sessions that precede unexpected process spawning, file modifications outside normal working directories, or configuration changes with no corresponding change-management record. Anomalous activity immediately following an admin login warrants investigation.
  • Monitor for indicators of compromise as directed by SonicWall Technical Support: the vendor advisory explicitly recommends contacting support for IoC review and, if IoCs are found, re-imaging hardware appliances or redeploying virtual instances and resetting all credentials and TOTP tokens.

Remediation

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see References) guidance and CISA’s “Forensics Triage Requirements” (see References). 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.
Federal (FCEB) remediation due date
September 5, 2026

Additional hardening

  • Upgrade SMA8200v, SMA6210, and SMA7210 appliances to firmware 12.4.3-03526 or 12.5.0-02952 (both platform-hotfix releases); see the vendor advisory in References for download instructions via mysonicwall.com.
  • Restrict AMC access to a dedicated, out-of-band management network or management VLAN reachable only from trusted administrator workstations, reducing the pool of sessions from which a credential-bearing attacker could reach the injection point.
  • Enforce multi-factor authentication on all AMC administrator accounts and audit the full list of accounts with administrative access, removing any that are unnecessary or unrecognized.
  • If IoCs are detected following a forensic review, re-image hardware appliances or redeploy virtual instances, then rotate all administrator and user passwords and reset all TOTP tokens before returning the appliance to service.

Key dates

Published (NVD)
September 1, 2026
Added to CISA KEV
September 2, 2026
Remediation deadline
September 5, 2026
Last updated
September 3, 2026

References

Frequently asked questions

Does CVE-2026-83549 affect my FedRAMP authorization?

If SonicWall SMA1000 Appliances runs inside your authorization boundary, CVE-2026-83549 affects your FedRAMP authorization directly. The vulnerability is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, and its September 5, 2026 remediation deadline has already passed. An unpatched KEV inside your boundary is an assessor finding. An overdue one is visible to both your assessor and your sponsoring agency. At this point, you either remediate it or formally document the mitigation and the delay.

How does Knox help me handle CVE-2026-83549?

Knox does not patch SonicWall SMA1000 Appliances on your behalf. Under the FedRAMP shared-responsibility model, that remediation is yours to carry out. What Knox provides is the pre-authorized, single-tenant boundary to remediate within, along with continuous compliance monitoring and audit-artifact coverage that support your documentation for the next assessment. The fix belongs to your team; maintaining a defensible compliance posture while you apply it is not something you have to manage alone.

How does Knox's monitoring help with vulnerabilities like this?

Knox's automated continuous monitoring platform watches your environment continuously for newly disclosed vulnerabilities and compliance gaps, including issues like CVE-2026-83549. Exposure surfaces during ongoing monitoring rather than only when an assessor reviews your posture, giving your team time to act before a finding becomes a formal problem.

How do I get FedRAMP authorized with Knox?

Knox runs a FedRAMP-as-a-Service platform. It gives SaaS vendors a pre-authorized cloud boundary on AWS, Azure, and GCP. Your application inherits 60-80% of the required security controls. You reach FedRAMP authorization in about 90 days for roughly 90% less than the traditional $3.5M path. Book a meeting and Knox will map your path to authorization.

CVE-2026-83549's remediation deadline of September 5, 2026 has passed. What happens now?

An unremediated CVE-2026-83549 is already a Plan of Action and Milestones (POA&M) item. A growing POA&M list is precisely what turns a routine continuous-monitoring review into a difficult conversation with your sponsoring agency. Closing the finding out now and documenting the circumstances of the delay is what keeps your authorization intact and the agency relationship in good standing.

Ready to achieve FedRAMP authorization in 90 days or less?

Schedule a meeting to discuss scope, parse readiness, and map your company’s accelerated path to FedRAMP authorization.

Book a Meeting