dbcve.org
Sma 500v FirmwareOperating system · Sonicwall

CVE-2025-40596

HIGH · 7.3 CVSS v3.1 Published 2025-07-23
Fix available
A fix is available. Upgrade to 10.2.2.1-90sv or later.
See remediation →
82/100
Remediation priority · High
High EPSS Remotely reachable No privileges 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
A Stack-based buffer overflow vulnerability in the SMA100 series web interface allows remote, unauthenticated attacker to cause Denial of Service (DoS) or potentially results in code execution.

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

A stack-based buffer overflow vulnerability in the SMA100 series web interface allows remote, unauthenticated attackers to overflow a stack buffer via specially crafted HTTP requests, potentially achieving code execution or causing denial of service.

MitigationApply available vendor patches or firmware updates for the SMA100 series; if patches are unavailable, restrict network access to the web interface via firewall rules or VPN.

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
Sma 500v FirmwareOperating system
Affected:< 10.2.2.1-90sv
Sma 210 FirmwareOperating system
Affected:< 10.2.2.1-90sv
Sma 410 FirmwareOperating system
Affected:< 10.2.2.1-90sv

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 SMA device model
    Access the device console or web interface and locate the model number (Sma 210, Sma 410, or Sma 500v). This can also be found via the device label, physical inspection, or SNMP enumeration.
    Affected if The device is a Sonicwall SMA 210, SMA 410, or SMA 500v.
  2. Determine the installed firmware version
    Log into the SMA web interface and navigate to System > Status or Device > Overview to view the firmware version. Alternatively, use the CLI command 'show version' or check the firmware file loaded on the device.
    Affected if The firmware version cannot be determined or is below 10.2.2.1-90sv.
  3. Compare firmware version against the affected threshold
    Compare the installed firmware version number to 10.2.2.1-90sv. Note that any version lower than 10.2.2.1-90sv (including older 10.x branches) is within the affected range.
    Affected if The installed firmware version is lower than 10.2.2.1-90sv.
  4. Confirm the web interface is enabled
    Check device settings to verify the web-based management interface (HTTP/HTTPS) is currently enabled. This is typically found under Network > Interfaces or Management > Access Settings in the device configuration.
    Affected if The web interface is enabled and listening on HTTP or HTTPS ports.
  5. Verify network accessibility of the web interface
    Attempt to reach the device web interface from an external network or use network scanning tools to confirm ports 80/443 are exposed. Check firewall policies to determine if the management interface is accessible from untrusted networks.
    Affected if The web interface is accessible from untrusted or external network segments.

The environment is affected if the device is a SMA 210, 410, or 500v running firmware below version 10.2.2.1-90sv with the web interface enabled and accessible.

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 10.2.2.1-90sv or later
Fixed in 10.2.2.1-90sv
Interim mitigation

Apply available vendor patches or firmware updates for the SMA100 series; if patches are unavailable, restrict network access to the web interface via firewall rules or VPN.

Recommended fix Moderate confidence

10.2.2.1-90sv or later

  1. 1. Back up current SMA device configuration and verify backup integrity
  2. 2. Download firmware version 10.2.2.1-90sv or later from the official SonicWall support portal at support.sonicwall.com
  3. 3. Access the SMA web management interface using an administrator account
  4. 4. Navigate to System > Settings > Firmware Update or similar firmware management section
  5. 5. Upload the downloaded firmware file (10.2.2.1-90sv or later) to the device
  6. 6. Confirm the firmware upgrade and allow the device to reboot
  7. 7. After reboot, verify the new firmware version is installed correctly
  8. 8. Test critical functionality to confirm normal operations
Caveat Review SonicWall release notes for 10.2.2.1-90sv for any configuration or feature changes before upgrading

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

Fix this in Sma 500v Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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