# CVE-2026-6445: Information disclosure in FlashArray

> Low-privilege authenticated users can access sensitive information due to insufficient data path filtering in FlashArray Purity.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-w284-7936-m8j9

## What is CVE-2026-6445?

CVE-2026-6445 is a high-severity vulnerability in Everpure FlashArray, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-939 (Improper Authorization in Handler for Custom URL Scheme)

## Which versions are affected by CVE-2026-6445?


## How do I fix CVE-2026-6445?

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

## Is CVE-2026-6445 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6445 and fix it if it is affected.

What it is: CVE-2026-6445 is a high-severity vulnerability in Everpure FlashArray, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6445 in the wild and no public exploit code.

Affected product: Everpure 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-2026-6445/ (Markdown: https://insights.sbomify.com/CVE-2026-6445/index.md)
```

## Sources

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

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