# CVE-2025-2327: FlashArray KEK Logging Vulnerability

> Attackers with log access can retrieve Key Encryption Keys during rotation if RDL is configured, compromising data confidentiality.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-pxv2-r799-mj6c

## What is CVE-2025-2327?

CVE-2025-2327 is a medium-severity vulnerability in Pure Storage FlashArray, published on 16 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-2327?


## How do I fix CVE-2025-2327?

No fix has been published for CVE-2025-2327 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2327 being exploited?

There is no known exploitation of CVE-2025-2327 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2327 and fix it if it is affected.

What it is: CVE-2025-2327 is a medium-severity vulnerability in Pure Storage FlashArray, published on 16 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2327 in the wild and no public exploit code.

Affected product: Pure Storage FlashArray. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2327/ (Markdown: https://insights.sbomify.com/CVE-2025-2327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2327
- OSV: https://osv.dev/vulnerability/CVE-2025-2327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2327/
Summaries are generated and may contain mistakes; the official description above is the record.