Cyber Resilience

CVE-2026-0209

Published
14 April 2026
Modified
17 April 2026
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0038 31th percentile
Risk Priority 27 floored blend · peak EPSS

Summary

CVE-2026-0209 is a medium-severity Operator Precedence Logic Error (CWE-783) vulnerability in Purestorage (inferred from references). Its CVSS base score is 6.9 (Medium).

Operationally, ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-783

Related Threats

CVEs Like This One

CVE-2024-27886Shared CWE-783
CVE-2024-31326Shared CWE-783
CVE-2024-34720Shared CWE-783
CVE-2025-24210Shared CWE-783
CVE-2026-25233Shared CWE-783
CVE-2024-34723Shared CWE-783
CVE-2024-31331Shared CWE-783
CVE-2024-34726Shared CWE-783
CVE-2024-20314Shared CWE-783
CVE-2024-31335Shared CWE-783

Affected Assets

Purestorage
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis directly find incorrect evaluation results caused by precedence mistakes.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and coding rules can require constructs that eliminate ambiguous operator precedence.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate explicit parentheses and precedence rules that structurally prevent the logic error from being written.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, static analysis, testing) directly catch precedence errors while the control also addresses many other development risks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect logic errors caused by precedence issues.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes code review and testing that can catch precedence errors.

A.8.28 Secure coding partial match
prevents

Secure coding standards and guidelines directly address operator precedence mistakes.

References