CVE-2026-35066
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 · uneditedDell PowerFlex Manager, version(s) prior to 5.1.0.1, contain(s) an Improper Access Control vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to denial of service.
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 confidenceDell PowerFlex Manager prior to version 5.1.0.1 contains an improper access control vulnerability that allows a low-privileged attacker with remote network access to trigger a denial of service condition. The vulnerability stems from insufficient validation of access permissions, enabling authenticated users with limited privileges to disrupt service availability.
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< 4.5.5.2>= 4.6.0, < 5.1.0.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm Dell PowerFlex Manager is installedLocate the PowerFlex Manager installation. Typically found at /opt/dell/powerflex_manager or check system services for 'powerflex-manager' or 'sdman'. Use command: systemctl list-units --all | grep -i powerflex or ps aux | grep -i powerflexAffected if The product is not Dell PowerFlex Manager (this CVE does not apply)
-
Determine the installed PowerFlex Manager versionRun the version check command for PowerFlex Manager. Common methods: /opt/dell/powerflex_manager/bin/sdman -version, or check /opt/dell/powerflex_manager/version.txt, or look in the About section of the management UI if accessibleAffected if Unable to determine the version - manual investigation required
-
Compare installed version against affected rangesThe affected versions are: < 4.5.5.2 OR >= 4.6.0 but < 5.1.0.1. Check if your installed version falls into either of these ranges. Note that version 4.5.5.2 and 5.1.0.1 are NOT affectedAffected if Installed version is less than 4.5.5.2 OR is 4.6.0 through 5.1.0.0
-
Verify remote network access is enabledCheck if the PowerFlex Manager UI or API is exposed to network interfaces other than localhost. Review firewall rules, reverse proxy configurations, or load balancer settings that expose the management interface. Look for listening services on non-loopback addresses: netstat -tuln | grep -E '4443|443|8443' (common PowerFlex ports)Affected if Remote network access to the management interface is exposed to untrusted networks
-
Check for low-privileged user accountsReview user accounts in PowerFlex Manager. Low-privileged users (non-admin roles) with authentication credentials could exploit this vulnerability. Use the admin UI to list users or query the user database if direct access is availableAffected if Low-privileged authenticated users exist in the system
Environment is affected if Dell PowerFlex Manager is installed with a version less than 4.5.5.2, or between 4.6.0 and 5.1.0.0, AND the management interface is remotely accessible AND low-privileged user accounts exist.
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 · scoped4.5.5.25.1.0.1
Upgrade Dell PowerFlex Manager to version 5.1.0.1 or later to address the improper access control vulnerability. If immediate upgrading is not feasible, consider network segmentation and restricting remote access to trusted users only to reduce the attack surface.
5.1.0.1 or later
- 1. Identify the current installed version of PowerFlex Manager by accessing the management interface or using the system inventory
- 2. Download PowerFlex Manager version 5.1.0.1 (or later) from the Dell support portal at www.dell.com
- 3. Review the upgrade prerequisites and documentation specific to your current version
- 4. Create a complete backup of the current PowerFlex Manager configuration and data
- 5. Schedule a maintenance window as the upgrade may require downtime
- 6. Follow the official Dell upgrade procedure to install version 5.1.0.1 or later
- 7. After upgrade, verify the new version is correctly installed and all services are running
- 8. Test critical PowerFlex Manager functionalities to confirm normal operation
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-35066 — 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-35066 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