CVE-2026-15263: Everpure Pure Storage Extension for Windows Admin Center · Improper Input Validation
Affects Everpure Pure Storage Extension for Windows Admin CenterSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 1.1.180 soon.
Data as of 18 Nov 2026, 14:35 UTC
Thin evidence
One scorer or none| CNA (Everpure) | CVSS 4.0 | 7.1 |
|---|
- Patch
- Available – fixed in 1.1.180
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 17 Nov 2026.
What to do
Upgrade Everpure Pure Storage Extension for Windows Admin Center to 1.1.180.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EverpurePure Storage Extension for Windows Admin Center | Affected
| Fixed in
|
AI-suggested
A fix for this vulnerability is available in Everpure Pure Storage Extension for Windows Admin Center version 1.1.180. Users should upgrade to this version or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-15263 is a server-side request forgery (SSRF) vulnerability in the Everpure Pure Storage Extension for Windows Admin Center. It affects versions prior to 1.1.180 and allows an authenticated Gateway User to redirect the management gateway to unintended hosts. This could expose stored FlashArray credentials and API tokens, potentially enabling unauthorized access to the managed FlashArray. The vulnerability has a high severity score of 7.1 and has been fixed in version 1.1.180.