CVE-2026-6444
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 · uneditedA flaw exists in the FlashArray Purity management interface where an authenticated low-privileged user may, under specific conditions, access functionality beyond their assigned privileges.
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 confidenceA privilege escalation vulnerability exists in FlashArray Purity management interface where an authenticated low-privileged user can access functionality beyond their assigned role permissions under specific conditions. This bypasses the intended role-based access control (RBAC) boundaries of the storage array's management plane.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 FlashArray Purity versionAccess the Purity management interface (GUI or CLI) and locate the version information, typically found in System > About or via the 'purectl version' commandAffected if The installed version has not received the CVE-2026-6444 patch and contains the RBAC bypass vulnerability
-
Confirm management interface is accessibleVerify that the Purity management interface (web GUI or API) is network-reachable. Check if port 443 or the management IP is exposedAffected if The management interface is exposed to network segments where low-privileged users can access it
-
Review user role assignmentsIn Purity GUI, navigate to Settings > Users & Roles or use 'purectl user list' to enumerate all users and their assigned rolesAffected if There are users assigned to non-administrative roles (e.g., readonly, operator) who may have elevated access
-
Test for RBAC bypass behaviorLog in with a low-privilege user account and attempt to access administrative features such as creating/deletin storage volumes, modifying alerts, or changing system settings that should be restricted to admin rolesAffected if A low-privileged user can perform actions outside their assigned role permissions, confirming the bypass
-
Examine audit logs for unauthorized privilege useCheck Purity audit logs (Settings > Audit Logs or via API) for actions performed by users with non-admin roles that involve administrative functionsAffected if Audit logs show low-privileged users executing administrative-level operations
A user is affected if they run a FlashArray Purity version where authenticated low-privileged users can bypass assigned role restrictions to perform administrative actions.
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.
From vendor dataReview all user role assignments in the Purity interface to ensure alignment with least-privilege principles; coordinate with Pure Storage for applicable patches addressing the privilege escalation vector.
- Consultation8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6444 — 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-6444 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