dbcve.org
Sma6210 FirmwareOperating system · Sonicwall

CVE-2026-4114

MEDIUM · 6.6 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 12.4.3-03387 / 12.5.0-02624 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Improper handling of Unicode encoding in SonicWall SMA1000 series appliances allows a remote authenticated SSLVPN admin to bypass AMC TOTP authentication.

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 · moderate confidence

The SonicWall SMA1000 series has a flaw in Unicode encoding handling that allows an authenticated SSLVPN administrator to bypass AMC (Advanced Mobile Connector) TOTP two-factor authentication. This authentication bypass occurs due to improper parsing or validation of Unicode-encoded inputs during the TOTP verification process.

MitigationApply available vendor patches or firmware updates for the SMA1000 series that address Unicode encoding handling in the AMC TOTP authentication flow. Until patched, consider additional compensating controls such as enhanced monitoring of admin authentication events and restricting SSLVPN admin access scope.

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.

NVD · CPE data
Sma6210 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma6200 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma7200 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma7210 FirmwareOperating system
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624
Sma8200vApplication
Affected:< 12.4.3-03387>= 12.5.0, < 12.5.0-02624

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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.

  1. Identify SMA1000 model
    Access the SMA web console or run 'get system info' command via CLI to confirm the device model is one of: SMA6210, SMA6200, SMA7200, SMA7210, or SMA8200v
    Affected if Device is not one of these five models - the vulnerability does not apply
  2. Check firmware version
    In the SMA web console, navigate to System > Status or run 'version' command via CLI to obtain the installed firmware version number
    Affected if Version is < 12.4.3-03387 OR (version >= 12.5.0 AND version < 12.5.0-02624) - falls within affected ranges
  3. Verify SSLVPN admin access is enabled
    In the SMA web console, navigate to Users > Administrator Settings or check if SSLVPN admin portal is accessible externally via https://<device-ip>/svpn/
    Affected if SSLVPN admin interface is enabled and accessible - required condition for exploitation
  4. Confirm AMC TOTP is configured
    In the SMA web console, navigate to Users > Mobile Devices > Advanced Mobile Connector or check if TOTP-based two-factor authentication is enabled for administrators
    Affected if AMC TOTP two-factor authentication is configured - this is the specific authentication mechanism that can be bypassed

User is affected if they run a vulnerable SMA1000 model (SMA6210/6200/7200/7210/8200v) with firmware in the affected version ranges AND have SSLVPN admin access enabled with AMC TOTP configured.

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.

dbcve · scoped
Upgrade available Upgrade to 12.4.3-03387 / 12.5.0-02624 or later
Fixed in 12.4.3-0338712.5.0-02624
Interim mitigation

Apply available vendor patches or firmware updates for the SMA1000 series that address Unicode encoding handling in the AMC TOTP authentication flow. Until patched, consider additional compensating controls such as enhanced monitoring of admin authentication events and restricting SSLVPN admin access scope.

Recommended fix High confidence

12.4.3-03387 or later, or 12.5.0-02624 or later

  1. 1. Identify the current firmware version of the affected SonicWall SMA appliance via the web management interface or CLI.
  2. 2. Download the fixed firmware version from the official SonicWall support portal (psirt.global.sonicwall.com).
  3. 3. If currently on firmware < 12.4.3-03387, upgrade to version 12.4.3-03387 or later.
  4. 4. If currently on firmware >= 12.5.0 and < 12.5.0-02624, upgrade to version 12.5.0-02624 or later.
  5. 5. Verify the upgrade was successful and confirm the new firmware version in the management interface.
  6. 6. Test AMC TOTP authentication functionality to confirm the vulnerability is resolved.
Caveat Review SonicWall release notes for any feature changes or migration considerations between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sma6210 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4114 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

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