# CVE-2026-67262: Missing authorization in PowerStore 1000T

> An attacker with host access can bypass LUN access controls to read or write unauthorized storage data in Dell PowerStore systems.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-xmq5-758c-5pfg

## What is CVE-2026-67262?

CVE-2026-67262 is a high-severity missing authorization vulnerability in Dell PowerStore 1000T, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dell PowerStore contains a Missing Authorization vulnerability. An attacker with access to a mapped host could exploit this vulnerability to read from or write to LUNs that the host is not authorized to access, bypassing per-initiator LUN access controls and leading to protection mechanism bypass.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-67262?


## How do I fix CVE-2026-67262?

No fix has been published for CVE-2026-67262 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67262 being exploited?

There is no known exploitation of CVE-2026-67262 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67262 and fix it if it is affected.

What it is: CVE-2026-67262 is a high-severity missing authorization vulnerability in Dell PowerStore 1000T, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67262 in the wild and no public exploit code.

Affected product: Dell PowerStore 1000T. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67262/ (Markdown: https://insights.sbomify.com/CVE-2026-67262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67262
- OSV: https://osv.dev/vulnerability/CVE-2026-67262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67262/
Summaries are generated and may contain mistakes; the official description above is the record.