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.
Why It Matters
Analysis dossierWhy It Matters
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.
Immediate Attention
Yes
Unknown
Risk basis: CISA KEV exploitation signal; HIGH severity; Known exploitation signal from CISA KEV or ransomware metadata
Affected Products & Remediation
3 source-backed productsVendor or catalog guidance (source)
- CISA KEV: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Listed
- Exploited (source statement)
- Yes
- Publicly disclosed (source)
- Unknown
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched command-injection (CWE-78); local-privilege-escalation (CVSS AV:L, CVSS PR:L)
Exposure
- Identify installations of the affected product and compare versions with the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · A weakness class does not establish local exposure. · Rule command-injection
- Identify hosts reporting this CVE, prioritising shared or multi-user systems.Telemetry: DeviceTvmSoftwareVulnerabilities · A local, low-privilege vector matters most where untrusted users can run code. · Rule local-privilege-escalation
Exploitation evidence
- Review command interpreters spawned by the affected service or application.Telemetry: DeviceProcessEvents · Unexpected process lineage can support command-injection hunting. · Rule command-injection
Show more (2)
Exploitation evidence
- Look for low-privileged processes spawning SYSTEM or root-level child processes on affected hosts.Telemetry: DeviceProcessEvents · Hunting hypothesis from the CVSS vector; privilege transitions are a focused starting point, not evidence of attack. · Rule local-privilege-escalation
Response
- Confirm the vendor mitigation or fixed version on affected assets.Telemetry: DeviceTvmSoftwareVulnerabilities · Inventory checks can verify remediation. · Rule command-injection
CISA KEV Record
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
Change History & Source Data
— No recorded material change
- CNA / source
- PSIRT@sonicwall.com
- Record status · verification
- NEW · CISA KEV confirmed
- CPE
- cpe:2.3:a:sonicwall:sma8200v:*:*:*:*:*:*:*:*, cpe:2.3:a:sonicwall:sma8200v:-:*:*:*:*:*:*:*, cpe:2.3:o:sonicwall:sma6210_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:sonicwall:sma6210:-:*:*:*:*:*:*:*, cpe:2.3:o:sonicwall:sma7210_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:sonicwall:sma7210:-:*:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-83549"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel descCorrelated briefings
— No published briefing references this CVE