Skip to content
vulnerability

CVE-2026-83549

7.8
High
KEV · Exploited in wildEPSS 10%Patch available

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.

exploited
Yes, in CISA KEV since 2 Sept 2026fix by 5 Sept 2026 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 9.9%
Published 1 Sept 2026Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply 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.

triage
server-sideruntimeWAF can block: noAV · localCWE-78· OS Command Injection

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: shlex/execve-style APIs

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2026-83549 being exploited?

Yes. CVE-2026-83549 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-83549?

CVE-2026-83549 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-83549?

Yes. A fix has been recorded for CVE-2026-83549. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-83549 affect?

CVE-2026-83549 affects sonicwall:sma8200v, sonicwall:sma6210_firmware, sonicwall:sma7210_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
sonicwall:sma8200vsonicwall:sma6210_firmwaresonicwall:sma7210_firmware
affected versions
SonicWall SMA1000
  • affected12.4.3-03453 (platform-hotfix) and older versions
  • affected12.5.0-02835 (platform-hotfix) and older versions

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 Metasploit module

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 3 Sept 2026 (SSVC 2.0.3).

timeline

  1. 1 Sept 2026Published
  2. 2 Sept 2026Added to CISA KEV (exploited in the wild) · same day later
  3. 3 Sept 2026CISA SSVC assessment: exploitation active · 1 day later
  4. 5 Sept 2026CISA remediation due date (US federal agencies) · 2 days later
  5. 21 Sept 2026CVE record last updated · 17 days later
  6. 2 Nov 2026Analysed by vulneraibility.com · 42 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 1 advisory, 1 link

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved