# CVE-2026-0209: Business logic in FlashArray

> Administrative conditions may cause FlashArray Purity to apply snapshot retention policies incorrectly, potentially leading to unintended data deletion or retention.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/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:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-jhcx-2f94-4747

## What is CVE-2026-0209?

CVE-2026-0209 is a medium-severity vulnerability in PureStorage FlashArray, published on 14 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Under certain administrative conditions, FlashArray Purity may apply snapshot retention policies earlier or later than configured.

Weakness: CWE-783 (Operator Precedence Logic Error)

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


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

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

## Is CVE-2026-0209 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0209 is a medium-severity vulnerability in PureStorage FlashArray, published on 14 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0209 in the wild and no public exploit code.

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

## Sources

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

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