CVE-2026-35065
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) a Missing Authentication for Critical Function vulnerability. An unauthenticated attacker with adjacent network access could potentially exploit this vulnerability, leading to Code execution, Denial of service, Information disclosure, Information tampering, Remote execution, Script injection, and Unauthorized access.
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 · high confidenceDell PowerFlex Manager versions prior to 5.1.0.1 contain a missing authentication vulnerability for critical functions. An unauthenticated attacker with adjacent network access can exploit this to execute code, cause denial of service, disclose or tamper with information, or gain unauthorized access to the system.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Confirm Dell PowerFlex Manager is installedCheck system for PowerFlex Manager components. Common locations: /opt/dell/powerflex_manager, /usr/local/powerflex, or check for service processes like 'powerflex-manager' via 'ps aux | grep -i powerflex' or 'systemctl list-units | grep -i powerflex'Affected if PowerFlex Manager is not found on the system (not affected)
-
Identify installed PowerFlex Manager versionRun 'rpm -qa | grep -i powerflex' or check /opt/dell/powerflex_manager/version file, or use 'cat /opt/dell/powerflex_manager/etc/version' if directory exists. Also check the web UI login page for version display or check the installer metadata.Affected if Version cannot be determined or is not PowerFlex Manager (inconclusive)
-
Compare installed version against affected rangesVersion must meet ONE of these conditions to be vulnerable: less than 4.5.5.2, OR greater than or equal to 4.6.0 but less than 5.1.0.1. Versions 4.5.5.2 through 4.6.0 (exclusive) and 5.1.0.1 and later are NOT affected.Affected if Installed version is < 4.5.5.2 OR (>= 4.6.0 AND < 5.1.0.1)
-
Assess network exposureCheck if the PowerFlex Manager management interface (typically ports 443, 8443, or custom ports) is accessible from adjacent network segments. Review firewall rules: 'iptables -L -n' or 'firewall-cmd --list-all'. Check network interfaces and binding addresses in configuration files under /opt/dell/powerflex_manager/etc/Affected if Management interface is exposed to adjacent/untrusted networks (increases exposure risk)
-
Verify if critical functions lack authenticationReview configuration files in /opt/dell/powerflex_manager/etc/ for authentication settings. Check API endpoints accessible without credentials by attempting unauthenticated requests to common paths like /api/v1/ or /rest/. Compare configuration against Dell documentation for expected authentication settings.Affected if Critical APIs or functions are accessible without authentication credentials
System is affected if Dell PowerFlex Manager is installed AND the installed version falls within < 4.5.5.2 or >= 4.6.0 to < 5.1.0.1 AND the management interface is accessible from the network.
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 remediate this vulnerability. Network segmentation should be applied to limit adjacent network attack surface as a compensating control.
5.1.0.1 or later
- 1. Back up all critical data and configurations before initiating any upgrade
- 2. Obtain PowerFlex Manager version 5.1.0.1 or later from the Dell support portal at www.dell.com
- 3. Review Dell PowerFlex Manager upgrade documentation for your specific current version
- 4. Schedule a maintenance window as the upgrade process may require system downtime
- 5. Follow Dell's recommended upgrade procedure for your PowerFlex Manager deployment
- 6. After completing the upgrade, verify that all services and components are running correctly
- 7. Confirm the vulnerability has been remediated by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35065 — 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-35065 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