CVE
Dell Ansible Storage for PowerStore, versions prior to 3.9.0, contains an Improper Certificate Validation vulnerability in the API client…
- Exploited
- No known exploitation
- Fix
- Fixed in 3.9.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.9.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dell Ansible Storage for PowerStore contains an improper certificate validation flaw in its API client component. An attacker on the network can exploit it without logging in, which could expose information and allow unauthorized access.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Dell Ansible Storage for PowerStore, versions prior to 3.9.0, contains an Improper Certificate Validation vulnerability in the API client component. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to information exposure and unauthorized access.
Who should check
Teams running Dell Ansible Storage for PowerStore before 3.9.0 that use its API client component.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.4/10CVSS 7.4
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.9.0.
Workaround: Explicitly enable certificate verification by setting verify=True
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-91871 (Dell Ansible Storage for PowerStore, versions prior to 3.9.0, contains an Improper Certificate Validation vulnerability in the API client…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-91871 (entry last updated 2026-11-11):
Affected:
- Dell Ansible Storage for PowerStore: version range not reported
Fixed versions: 3.9.0.
Conditions (all must be true for the bug to be hit):
- Dell Ansible Storage for PowerStore versions prior to 3.9.0 with the API client component. (source: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities)
- Certificate verification is not explicitly enabled (the verify option is not set to True). (source: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Explicitly enable certificate verification by setting verify=True (source: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities)
CISA KEV: CVE-2026-91871 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91871 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-91871
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-91871"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dell Ansible Storage for PowerStore
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-91871
Is CVE-2026-91871 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The API client in Dell Ansible Storage for PowerStore does not properly validate certificates, so connections to the PowerStore API may not confirm the server's identity. This can lead to information exposure and unauthorized access.Source: dell.com
Am I affected, and how do I check?
Versions of Dell Ansible Storage for PowerStore prior to 3.9.0 are affected when certificate verification is not explicitly enabled, meaning the verify option is not set to True. To check, look at the installed version and at whether verify=True is set in the API client configuration.Source: dell.com
How do I fix CVE-2026-91871?
Upgrade Dell Ansible Storage for PowerStore to version 3.9.0 or later, which contains the fix. Until the upgrade is done, explicitly enable certificate verification by setting verify=True.Source: dell.com