CVE-2026-35067
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 adjacent network access could potentially exploit this vulnerability, leading to Elevation of privileges 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 an improper access control vulnerability that allows a low-privileged attacker with adjacent network access to escalate privileges and 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 Dell PowerFlex Manager versionLocate the installed version of Dell PowerFlex Manager in the system. This is typically found in the product's about page, administrative console, or via the management API documentation for PowerFlex Manager.Affected if The installed version is < 4.5.5.2 OR (>= 4.6.0 AND < 5.1.0.1)
-
Verify version falls outside vulnerable rangesCompare your installed PowerFlex Manager version against the affected ranges. Versions 4.5.5.2 through 4.6.0 (exclusive) and 5.1.0.1 and later are not affected.Affected if Your version is NOT 5.1.0.1 or later and NOT in a safe patch version above the affected ranges
-
Confirm adjacent network exposureAssess whether the PowerFlex Manager interface is accessible from adjacent network segments. This vulnerability requires adjacent network access for exploitation.Affected if The management interface is exposed to adjacent network segments without proper network segmentation
You are affected if your installed PowerFlex Manager version is prior to 5.1.0.1 and falls within the ranges < 4.5.5.2 or >= 4.6.0, < 5.1.0.1
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.
Dell PowerFlex Manager 5.1.0.1 or later
- 1. Identify the current Dell PowerFlex Manager version installed in your environment
- 2. Verify the current version is affected: < 4.5.5.2 OR >= 4.6.0 and < 5.1.0.1
- 3. Plan the upgrade to version 5.1.0.1 or later, ensuring appropriate backup and maintenance windows
- 4. Review Dell PowerFlex Manager upgrade documentation for prerequisites and procedures
- 5. Perform the upgrade following Dell's official upgrade path
- 6. Verify the new version is 5.1.0.1 or later after completion
- 7. Validate that the Improper Access Control vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35067 — 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-35067 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