Skip to main content

Pure Storage FlashArray CVE-2026-6445

| EUVDEUVD-2026-35792 HIGH
Improper Authorization in Handler for Custom URL Scheme (CWE-939)
2026-06-09 Everpure GHSA-w284-7936-m8j9
8.7
CVSS 4.0 · Vendor: Everpure
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege Purity credentials
  2. Delivery
    Reach FlashArray management endpoint
  3. Exploit
    Send crafted request to vulnerable handler
  4. Execution
    Bypass authorization filtering
  5. Impact
    Exfiltrate sensitive array data

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V4 - API and Web Service Improper authorization in handler
Exploitation Conditions

The attacker must possess valid authenticated credentials at a low privilege level on the FlashArray Purity management interface (CVSS PR:L), and must have network reachability to that interface (AV:N) - typically a management VLAN or directly exposed array endpoint. No user interaction is required (UI:N) and attack complexity is low (AC:L), but exploitation is limited to Purity versions 6.5.0-6.5.8 and 6.10.0-6.10.5; arrays on 6.5.9+ or 6.10.6+ (or other Purity trains) are out of scope per EUVD. Risk is further bounded by the fact that exposure requires an existing authenticated foothold, so environments with strict RBAC, MFA on Purity accounts, and isolated management networks materially reduce realistic exploitability.

Impact

Signals are mixed: CVSS 4.0 rates the issue 8.7 (High) driven by network attack vector, low complexity, low privileges, and high impact across all three confidentiality, integrity, and availability dimensions, yet the original description characterizes the impact as information exposure rather than write/destroy. SSVC counterbalances the CVSS with 'Exploitation: none' and 'Automatable: no', and there is no CISA KEV listing or public POC, meaning no evidence of in-the-wild activity. The CVSS VI:H/VA:H ratings appear inconsistent with a pure information-disclosure flaw described in the text - defenders should verify with Pure Storage whether the disclosed data enables follow-on integrity or availability impact, or whether the vector overstates the consequence. Because exploitation requires an authenticated account on the storage array, real-world risk is concentrated at organizations with broad admin access to FlashArray management planes; for hardened environments with tight RBAC this is a moderate-priority patch, while for environments with shared low-privilege accounts it warrants urgent remediation.

Exploit ScenarioDerived

An attacker who has obtained a low-privilege Purity account - for example a read-only monitoring credential leaked from a CI system or a help-desk operator account - issues crafted requests against the FlashArray management interface and receives data that should be restricted to administrators, such as volume contents metadata, replication targets, or credential material. With no public POC identified, exploitation today would require independent vulnerability research or vendor-detail leakage; SSVC rates the issue as not automatable, so mass scanning is unlikely.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 09, 2026

Information disclosure in Pure Storage FlashArray Purity (versions 6.5.0-6.5.8 and 6.10.0-6.10.5) allows an authenticated low-privileged user to retrieve sensitive data via insufficiently filtered data paths. The flaw carries a CVSS 4.0 score of 8.7 with high confidentiality, integrity, and availability impact, but SSVC indicates no public exploitation and the attack is not automatable. No public exploit has been identified at the time of analysis.

RemediationAI

No vendor-released patched version is independently confirmed in the provided data; upgrade beyond the affected ranges (past 6.5.8 on the 6.5 train and past 6.10.5 on the 6.10 train) once Pure Storage publishes a fixed Purity release, consulting the security bulletins page at https://support.purestorage.com/bundle/m_security_bulletins/page/Pure_Security/topics/concept/c_security_bulletins.html for the exact target version. As compensating controls until the patch is staged, tighten Purity RBAC so that low-privilege roles cannot reach the management API, restrict the management network to a dedicated admin VLAN with jump-host access only, rotate credentials for any low-privilege Purity accounts that may have been shared, and enable audit logging on the array to detect anomalous read activity from low-privilege users. Trade-offs: locking down the management VLAN may break monitoring integrations that poll the API, and disabling low-privilege accounts can disrupt automation pipelines that rely on read-only credentials.

Affected VersionsENISA

FlashArray 6.10.0 ≤6.10.5
FlashArray 6.5.0 ≤6.5.8

Affected Packages

euvd flasharray no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FlashArray Purity is the operating environment that powers Pure Storage's all-flash enterprise storage arrays, providing block, file, and management APIs over the network. The weakness is classified as CWE-939 (Improper Authorization in Handler for Custom URL Scheme), indicating that specific request paths or handlers fail to apply adequate authorization filtering before returning data. In practice this means certain administrative or data-retrieval endpoints honor requests from low-privileged authenticated sessions and surface information that should be gated behind higher-privilege roles. The CPE string 'cpe:2.3:a:everpure:flasharray' appears to reference the FlashArray product family within the Purity environment, though the vendor namespace deviates from typical Pure Storage CPE entries and should be cross-checked against the vendor advisory.

Know when Flasharray gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Everpure) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Everpure) · only source for this CVE.

CVSS VectorVendor: Everpure

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Jun 09, 2026 - 20:22 NVD
8.7 (HIGH)
CVE Published
Jun 09, 2026 - 18:40 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

A flaw exists in FlashArray Purity where insufficient filtering of certain data paths could expose sensitive information to an authenticated user with low privileges.

Executive ViewAI

Why It Matters

Pure Storage FlashArray Purity versions 6.5.0-6.5.8 and 6.10.0-6.10.5 contain an information disclosure vulnerability (CVSS 8.7) allowing authenticated low-privileged users to extract sensitive data through inadequately filtered API paths. Organizations deploying affected versions face unpatched data exposure risk, requiring immediate access controls and vendor engagement to protect critical storage infrastructure.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Network segmentation-restrict FlashArray management interface access to authorized administrators only; (2) Enforce multi-factor authentication for all administrative accounts; (3) Minimize and audit low-privileged user accounts with system access; (4) Enable comprehensive audit logging and implement real-time alerts for sensitive data access; (5) Conduct quarterly access reviews to remove excessive privileges; (6) Document this vulnerability in risk register and escalate for patch monitoring priority.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy