CVE
Dell Terraform Provider for PowerStore, versions prior to 1.3.1 , contains a vulnerability that may cause sensitive authentication data to…
Only affects Dell Terraform Provider for PowerStore before 1.3.1 when debug dumping is enabled via GOPOWERSTORE_DEBUG=true. Fixed in version 1.3.1 or later.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in Version 1.3.1 or later
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Dell Terraform Provider for PowerStore, versions prior to 1.3.1 Debug dumping enabled via GOPOWERSTORE_DEBUG=true, which is not a production setting
- 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? →
- 20/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? →
- Specific setups only
- 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 Terraform Provider for PowerStore, prior to the fixed release, may insufficiently redact sensitive authentication data in its diagnostic logs. An unauthenticated attacker can exploit this remotely, without logging in, to read that exposed information.
Read the original description
Dell Terraform Provider for PowerStore, versions prior to 1.3.1 , contains a vulnerability that may cause sensitive authentication data to be insufficiently redacted in diagnostic logs. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to information exposure.
Who should check
Teams running the Dell Terraform Provider for PowerStore at versions prior to 1.3.1, including those with GOPOWERSTORE_DEBUG debug dumping enabled
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Dell Terraform Provider for PowerStore, versions prior to 1.3.1 Debug dumping enabled via GOPOWERSTORE_DEBUG=true, which is not a production settingUpgrade to a fixed version: Version 1.3.1 or later.
Workaround: Do not enable GOPOWERSTORE_DEBUG=true in production. If debug dumping must be enabled temporarily for troubleshooting, restrict access to the resulting log output and rotate the DELL-EMC-TOKEN afterward.
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-91891 (Dell Terraform Provider for PowerStore, versions prior to 1.3.1 , contains a vulnerability that may cause sensitive authentication data to…), 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-91891 (entry last updated 2026-11-11):
Affected:
- Dell Terraform Provider for PowerStore: version range not reported
Fixed versions: Version 1.3.1 or later.
Conditions (all must be true for the bug to be hit):
- Dell Terraform Provider for PowerStore, versions prior to 1.3.1 (source: https://www.dell.com/support/kbdoc/en-in/000515434/dsa-2026-433-security-update-for-dell-terraform-provider-for-dell-storage-multiple-vulnerabilities)
- Debug dumping enabled via GOPOWERSTORE_DEBUG=true, which is not a production setting (source: https://www.dell.com/support/kbdoc/en-in/000515434/dsa-2026-433-security-update-for-dell-terraform-provider-for-dell-storage-multiple-vulnerabilities)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Do not enable GOPOWERSTORE_DEBUG=true in production. If debug dumping must be enabled temporarily for troubleshooting, restrict access to the resulting log output and rotate the DELL-EMC-TOKEN afterward. (source: https://www.dell.com/support/kbdoc/en-in/000515434/dsa-2026-433-security-update-for-dell-terraform-provider-for-dell-storage-multiple-vulnerabilities)
CISA KEV: CVE-2026-91891 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91891 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-in/000515434/dsa-2026-433-security-update-for-dell-terraform-provider-for-dell-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-91891
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-91891"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dell Terraform Provider 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-91891
Is CVE-2026-91891 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?
Sensitive authentication data may not be fully redacted in diagnostic logs, so it can appear in log output and be exposed.Source: dell.com
Am I affected, and how do I check?
Dell Terraform Provider for PowerStore versions prior to 1.3.1 are affected, and the issue relates to debug dumping enabled via GOPOWERSTORE_DEBUG=true. To check a setup, look at the provider version in use and whether GOPOWERSTORE_DEBUG is set to true.Source: dell.com
How do I fix CVE-2026-91891?
Upgrade to version 1.3.1 or later. Until then, do not enable GOPOWERSTORE_DEBUG=true in production.Source: dell.com