CVE-2026-4116

CVE-2026-4116 is a high-severity vulnerability in Sonicwall Sma6210 Firmware with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-176.

Key facts

Description

Improper handling of Unicode encoding in SonicWall SMA1000 series appliances allows a remote authenticated SSLVPN user to bypass Workplace/Connect Tunnel TOTP authentication.

Frequently asked questions

What is CVE-2026-4116?
Improper handling of Unicode encoding in SonicWall SMA1000 series appliances allows a remote authenticated SSLVPN user to bypass Workplace/Connect Tunnel TOTP authentication.
How severe is CVE-2026-4116?
CVE-2026-4116 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-4116 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-4116?
CVE-2026-4116 primarily affects Sonicwall Sma6210 Firmware. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-4116?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-4116 have an EU (EUVD) identifier?
Yes. CVE-2026-4116 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-20908.
When was CVE-2026-4116 published?
CVE-2026-4116 was published on 2026-04-09 and last updated on 2026-06-17.

References

Affected products (5)

More vulnerabilities in Sonicwall Sma6210 Firmware

All CVEs affecting Sonicwall Sma6210 Firmware →

Other CWE-176 vulnerabilities

Browse all CWE-176 vulnerabilities →