CVE-2026-0205
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 · uneditedA post-authentication Path Traversal vulnerability in SonicOS allows an attacker to interact with usually restricted services.
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 confidenceA post-authentication Path Traversal vulnerability in SonicOS allows authenticated attackers to manipulate file paths to access restricted services or resources that should otherwise be protected by access controls.
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< 6.5.5.2-28n>= 7.0.0.0, <= 7.0.1-5169>= 7.1.1-7040, < 7.3.2-7010>= 8.0.0-8035, < 8.2.0-8009CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed SonicOS firmware versionLog into the SonicWall management interface and navigate to System > Status, or use the CLI command 'show version' to retrieve the running firmware version and build number.Affected if The installed version falls within any of these ranges: < 6.5.5.2-28n; >= 7.0.0.0 through <= 7.0.1-5169; >= 7.1.1-7040 through < 7.3.2-7010; >= 8.0.0-8035 through < 8.2.0-8009
-
Verify the web-based management interface is enabledNavigate to Network > Interfaces in the SonicWall GUI and confirm the management interface (HTTP/HTTPS) is configured and active, or check via CLI with 'show interface management'.Affected if The management interface is exposed and accessible, which is required for authenticated attackers to exploit the path traversal flaw.
-
Confirm active administrator or user accounts existNavigate to Users > Local Users and Groups or use the CLI command 'show user local' to list configured accounts that could be leveraged for authentication.Affected if There are any locally configured accounts (including limited-privilege users) that could be compromised or used to authenticate and trigger the path traversal.
-
Review access control settings for management interfacesCheck the management access list under System > Administration and verify which IP addresses or networks are permitted to access the management interface.Affected if Management access is granted to untrusted networks or the internet, allowing external authenticated attackers to reach the vulnerable endpoint.
Your environment is affected if the installed SonicOS version matches one of the vulnerable ranges AND the management interface is accessible to an attacker who can obtain valid credentials.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data6.5.5.2-28n7.3.2-70108.2.0-8009
Apply vendor-supplied firmware updates for SonicOS and review admin access controls to ensure least-privilege principles are enforced for management interfaces.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0205 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0205 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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