# CVE-2026-26289: Subnet Solutions PowerSYSTEM Center Incorrect Authorization

> Authenticated users with limited permissions can access sensitive device account data via the REST API, bypassing administrative restrictions.

- **Severity:** High 8.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-cj84-4hc2-frh6

## What is CVE-2026-26289?

CVE-2026-26289 is a high-severity missing authorization vulnerability in Subnet Solutions PowerSYSTEM Center 2020, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PowerSYSTEM Center REST API endpoint for device account export allows an authenticated user with limited permissions to expose sensitive information normally restricted to administrative permissions only.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-26289 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26289 is a high-severity missing authorization vulnerability in Subnet Solutions PowerSYSTEM Center 2020, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26289 in the wild and no public exploit code.

Affected product: Subnet Solutions PowerSYSTEM Center 2020. 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-26289/ (Markdown: https://insights.sbomify.com/CVE-2026-26289/index.md)
```

## Sources

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

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