VulnerabilityPublished 16 Jun 2025

CVE-2025-2327: Pure Storage FlashArray · Sensitive Data in Logs

Affects Pure Storage FlashArraySource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Pure Storage FlashArray	Affected 6.0.0 – 6.8.0 9 affected builds	Fixed in–

AI-suggested

Immediate mitigation should focus on restricting access to system logs containing sensitive information. Implement strict role-based access controls (RBAC) and audit logging access to detect unauthorized attempts.
Disable or carefully review the use of Remote Data Locking (RDL) if it is not essential, as this feature triggers the logging of the KEK.
Monitor logs for any unexpected access or exfiltration attempts, using Security Information and Event Management (SIEM) tools with alerts for unusual log access patterns.
Coordinate with Pure Storage for upcoming patches or firmware updates addressing this vulnerability and plan timely deployment once available.
As a temporary workaround, consider log sanitization or filtering mechanisms to redact or encrypt sensitive key material before logs are stored or transmitted.
Conduct a thorough review of key management policies and ensure that KEKs are rotated regularly and stored securely outside of logs.
Train system administrators and security teams on the risks of sensitive data exposure in logs and enforce best practices for secure logging.
Implement network segmentation and multi-factor authentication (MFA) to reduce the risk of unauthorized privileged access that could exploit this vulnerability.

Description

A flaw exists in FlashArray whereby the Key Encryption Key (KEK) is logged during key rotation when RDL is configured.

Impact

For European organizations using Pure Storage FlashArray devices with RDL enabled, this vulnerability poses a risk to the confidentiality of encrypted data. If an attacker or malicious insider with administrative access can access system logs, they could extract the KEK and potentially decrypt sensitive data stored on the FlashArray. This could lead to data breaches involving personal data, intellectual property, or critical business information, undermining compliance with GDPR and other data protection regulations. The impact is particularly significant for sectors with stringent data security requirements such as finance, healthcare, government, and critical infrastructure. The exposure of KEK could also facilitate lateral movement within networks if attackers leverage decrypted data to escalate privileges or compromise additional systems. Although the vulnerability does not affect data integrity or availability directly, the loss of confidentiality can have severe reputational and financial consequences. Given the medium CVSS score and the requirement for high privileges, the threat is more relevant in scenarios where internal threat actors or attackers have already gained elevated access, emphasizing the need for strict access controls and monitoring. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation, especially in high-value environments prevalent in Europe.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.purestorage.com/category/m_pure_storage_product_security (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jun 2025, 16:49 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats