CVE-2026-2699
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 · uneditedCustomer Managed ShareFile Storage Zones Controller (SZC) allows an unauthenticated attacker to access restricted configuration pages. This leads to changing system configuration and potential remote 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 confidenceCustomer Managed ShareFile Storage Zones Controller (SZC) contains an authentication bypass vulnerability allowing unauthenticated attackers to access restricted administrative configuration pages. This enables modification of system settings which can lead to remote code execution.
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>= 5.0.0, < 5.12.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ShareFile SZC versionCheck the installed version of the Storage Zones Controller. This is typically found in the product's about page, installation directory, or by querying the installed packages/services. On Windows, check Program Files\Sharefile\StorageZones Controller\ or look in the Windows Registry under HKLM\SOFTWARE\Sharefile\StorageZonesController. On Linux, check /opt/sharefile/szc/ or the RPM/DEB package information.Affected if The installed version is 5.0.0 or higher but lower than 5.12.4 (e.g., 5.0.0, 5.5.1, 5.11.2 are all affected)
-
Verify configuration page access controlsAttempt to access the Storage Zones Controller administrative configuration pages without providing credentials. Common endpoints include /storagezonescontroller/, /admin/, or /configuration/ paths on the SZC web interface. Use a web browser or curl command: curl -I http(s)://<szc-host>/storagezonescontroller/configAffected if HTTP responses return 200 OK or display configuration interfaces without requiring login credentials (authentication bypass successful)
-
Inspect system for unauthorized configuration changesReview the Storage Zones Controller configuration files and settings for unexpected modifications. Check configuration files in the SZC installation directory, particularly any XML or JSON config files, and review the Windows Event Viewer Security logs or Linux audit logs for access attempts to configuration endpoints.Affected if Configuration files show changes not made by authorized administrators, or event logs contain numerous failed authentication attempts followed by successful unauthenticated access to admin pages
Your environment is affected if the installed ShareFile Storage Zones Controller version is between 5.0.0 and 5.12.3 inclusive AND the administrative configuration pages are accessible without authentication.
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.
dbcve · scoped5.12.4
Apply vendor-provided patches immediately and restrict network access to the Storage Zones Controller management interfaces until patched. Review access logs for signs of exploitation.
ShareFile Storage Zones Controller 5.12.4 or later
- Verify current installed version of ShareFile Storage Zones Controller
- Review ShareFile upgrade documentation at docs.sharefile.com for upgrade prerequisites
- Create a full backup of the current SZC configuration and data
- Ensure the upgrade is performed during a planned maintenance window
- Download ShareFile Storage Zones Controller version 5.12.4 or later from the official source
- Follow the official upgrade procedure documented by ShareFile/Citrix
- Verify the upgrade was successful by checking the SZC version
- Test that the access control vulnerability is remediated by confirming restricted configuration pages require authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2699 — 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-2699 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