CVE-2026-26289
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPowerSYSTEM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe PowerSYSTEM Center REST API endpoint for device account export lacks proper authorization enforcement, allowing authenticated users with limited/non-administrative permissions to access sensitive device account information (e.g., credentials, configuration data) that should be restricted to administrative users only.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm PowerSYSTEM Center installation and versionLocate the PowerSYSTEM Center installation directory and identify the installed product version. Check the 'About' or 'System Information' section within the application or check version files in the installation folder.Affected if The installed version falls within any affected version range for this CVE.
-
Verify REST API is enabledCheck the PowerSYSTEM Center configuration to confirm whether the REST API service is enabled and accessible. Look for API-related configuration files or service settings.Affected if The REST API is enabled and exposed to users.
-
Identify non-administrative users with API accessReview user accounts and their assigned roles/permissions within PowerSYSTEM Center. Specifically identify users who have API access but do not hold administrative privileges.Affected if There are authenticated users with limited or non-administrative permissions who have API access.
-
Inspect device account export API endpoint behaviorAttempt to access or review logs for the device account export endpoint using credentials of a non-administrative user. Check whether the endpoint returns sensitive device account information such as credentials or configuration data without verifying administrative privileges.Affected if The device account export endpoint returns sensitive credential or configuration data when accessed by non-administrative users.
-
Review API authorization controlsExamine the API endpoint configuration or source code for role-based access control (RBAC) enforcement on the device account export function. Verify whether administrative privilege verification occurs before returning sensitive data.Affected if The device account export API lacks proper RBAC checks or administrative privilege verification.
A user is affected if non-administrative authenticated users can retrieve sensitive device account credentials or configuration data through the REST API export endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement and enforce role-based access control (RBAC) checks on the device account export API endpoint to verify administrative privileges before returning sensitive data; restrict API access to trusted administrative personnel until the patch is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26289 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26289 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data