CVE-2026-35068
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability. A low privileged attacker with adjacent network access could potentially exploit this vulnerability, leading to information disclosure.
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 confidenceSQL injection vulnerability in Dell PowerFlex Manager allows a low-privileged attacker with adjacent network access to inject malicious SQL commands, potentially leading to unauthorized information disclosure from the database.
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
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 the installed PowerFlex Manager versionAccess the PowerFlex Manager administration interface or check system documentation for the currently deployed version numberAffected if The version falls outside the fixed releases (not 4.5.5.2 or 5.1.0.1 and later)
-
Compare against affected version rangesVerify if the installed version is either earlier than 4.5.5.2, or between 4.6.0.0 and 5.1.0.0 inclusiveAffected if The version matches the vulnerable ranges (< 4.5.5.2 OR >= 4.6.0 AND < 5.1.0.1)
-
Confirm network accessibility of management interfaceDetermine if the PowerFlex Manager web interface or API is accessible from adjacent network segmentsAffected if The management interface is exposed to network segments where untrusted users have adjacent access
-
Check for SQL-facing features in useIdentify if any database query functionality, reporting modules, or data export features are enabled in the deploymentAffected if Features that process SQL queries or interface with the database are active
You are affected if your PowerFlex Manager version is earlier than 4.5.5.2, or between 4.6.0.0 and 5.1.0.0, and the management interface is network-accessible to low-privileged users.
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 obtain the patched code that properly neutralizes special elements in SQL commands.
PowerFlex Manager 5.1.0.1
- 1. Identify current PowerFlex Manager version by navigating to the Admin or Settings section of the web interface, or running the appropriate version check command
- 2. Schedule a maintenance window and create a complete backup of the PowerFlex Manager system and associated data
- 3. Download PowerFlex Manager version 5.1.0.1 from Dell Support website (support.dell.com) using a valid Dell support account
- 4. Review Dell PowerFlex Manager upgrade documentation for version 5.1.0.1 to ensure all prerequisites are met
- 5. Apply the upgrade following the documented upgrade procedure (typically through the management interface or command-line tool provided by Dell)
- 6. Verify the upgrade was successful by checking the version number after completion
- 7. Confirm the SQL injection vulnerability is resolved by verifying the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.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 $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35068 — 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-35068 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