dbcve.org
Sma6210 FirmwareOperating system · Sonicwall

CVE-2026-4116

HIGH · 7.2 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 →
78/100
Remediation priority · High
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 user to bypass Workplace/Connect Tunnel 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 appliances have improper Unicode encoding handling that allows an authenticated SSLVVPN user to bypass TOTP (time-based one-time password) authentication for Workplace/Connect Tunnel connections. This is an authentication bypass vulnerability exploiting how the appliance processes Unicode characters in the authentication flow.

MitigationApply the vendor-supplied patch for SonicWall SMA1000 series and verify TOTP authentication is properly enforced after the update.

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

CVSS:3.1/AV:N/AC:L/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 the SMA100 appliance model
    Access the appliance admin interface or use the command line to determine the exact model number (Sma6210, Sma6200, Sma7200, Sma7210, or Sma8200v)
    Affected if The model is one of the SMA1000 series listed in the affected products
  2. Check the installed firmware version
    Log into the SMA1000 admin console and navigate to System > Status or use the CLI command 'version' to retrieve the current firmware version
    Affected if The firmware version is either less than 12.4.3-03387, or greater than or equal to 12.5.0 but less than 12.5.0-02624
  3. Verify SSLVPN is enabled
    Check the appliance configuration under VPN > SSLVPN or Connections > SSLVPN settings to confirm SSLVPN functionality is turned on
    Affected if SSLVPN is enabled and configured for user access
  4. Confirm TOTP authentication is configured
    Navigate to Users > Local Users or Authentication settings and verify that TOTP (time-based one-time password) is enabled for Workplace or Connect Tunnel connections
    Affected if TOTP is set as an authentication method for Workplace or Connect Tunnel VPN connections

You are affected if you have a SMA1000 series appliance (Sma6210, Sma6200, Sma7200, Sma7210, or Sma8200v) running vulnerable firmware and have both SSLVPN and TOTP enabled for Workplace or Connect Tunnel connections.

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 the vendor-supplied patch for SonicWall SMA1000 series and verify TOTP authentication is properly enforced after the update.

Recommended fix Moderate confidence

Upgrade to firmware version 12.4.3-03387 or later for the 12.4.x branch, or 12.5.0-02624 or later for the 12.5.x branch

  1. 1. Identify the current firmware version of the affected SonicWall SMA appliance via the web management interface or CLI.
  2. 2. Determine which firmware branch (12.4.x or 12.5.x) is currently in use.
  3. 3. Download the appropriate fixed firmware version from the official SonicWall support portal at psirt.global.sonicwall.com.
  4. 4. Back up the current appliance configuration through the web management interface (System > Settings > Export).
  5. 5. Upload the fixed firmware image through the web management interface (System > Settings > Firmware Management > Upload).
  6. 6. Follow the standard firmware upgrade procedure, ensuring stable power and network connectivity during the process.
  7. 7. After reboot, verify the new firmware version is installed and the appliance is operational.
  8. 8. Test that TOTP authentication for Workplace/Connect Tunnel is functioning correctly.
Caveat Review release notes for any configuration or feature changes between versions; test in staging environment before production deployment

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

Fix this in Sma6210 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4116 — 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-4116 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