/

CVE-2026-26289

Severity:

HIGH RISK

(8.2)

Broken Access Control / Missing Authorization

CVE-2026-26289

Awaiting Analysis

Vulnerability type

Category:

Broken Access Control / Missing Authorization

CWE:

CWE-863

Impact:

Exposure of Sensitive Information and Privilege Abuse

Severity:

HIGH RISK

(8.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The PowerSYSTEM Center REST API exposes a device account export endpoint that fails to properly enforce authorization, allowing users with limited permissions to access sensitive data intended only for administrators.

An authenticated but low-privileged user can leverage this flaw to export device account information and other sensitive details that should be restricted to higher-privileged roles.

Affected context

This vulnerability appears in deployments of PowerSYSTEM Center where:

  • The REST API is exposed to authenticated users with varying permission levels
  • Role- or permission-based checks are expected for administrative endpoints
  • The device account export endpoint is reachable to non-administrator accounts

It is most relevant in multi-tenant or shared administrative environments where low-privileged user accounts exist alongside high-privileged administrative roles.

Exploit preconditions

  • Attack surface: PowerSYSTEM Center REST API over the network
  • Required access: Valid, authenticated account with limited/standard user permissions
  • Trigger point: Calling the device account export REST API endpoint
  • Why exploitation is possible: The endpoint does not correctly verify that the caller has administrative or equivalent permissions before returning sensitive export data, resulting in a missing or incomplete authorization check.

Why this happens

The core issue aligns with CWE-863: Incorrect Authorization, where the system authenticates a user but fails to ensure they are authorized for a particular operation.

In this case, the device account export endpoint is either misconfigured or implemented without a strict role/permission check, treating any authenticated request as sufficiently privileged.

This reflects an insecure access control pattern where authorization logic is missing, inconsistent, or detached from the centralized policy used for other administrative actions.

Potential impact

  • Exposure of sensitive device account information to low-privileged users
  • Facilitation of further attacks through harvested credentials or configuration data
  • Escalation of operational capabilities by leveraging leaked administrative or device accounts
  • Compliance and privacy violations due to unauthorized access to protected information
  • Increased risk of lateral movement across managed systems using exposed account details

General mitigation guidance

Effective mitigation focuses on strengthening authorization checks and centralizing access control policy:

  • Enforce strict role- and permission-based authorization on all administrative REST API endpoints, including device account export.
  • Use a centralized authorization mechanism or middleware so that endpoints cannot bypass policy enforcement.
  • Adopt least-privilege role design so that ordinary users never inherit permissions to export sensitive configuration or account data.
  • Implement deny-by-default access patterns for sensitive operations, requiring explicit grants for administrative roles.
  • Review logging and access patterns for sensitive endpoints to validate that authorization decisions match policy expectations.

How teams detect issues like this

Detection typically involves combining code-level review with behavioral analysis:

  • Static analysis or manual code review to identify REST handlers that:
  • Only check for authentication but not specific roles/permissions
  • Bypass or duplicate the central access control mechanism
  • API specification and contract tests that assert role-based access rules for sensitive endpoints (e.g., export, backup, configuration).
  • Runtime monitoring of access logs to flag low-privileged accounts invoking administrative endpoints or downloading unusually sensitive payloads.
  • Periodic authorization audits where security or QA teams systematically test endpoints with various roles to spot missing checks.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-132-02.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-132-02

Frequently asked

questions

Yes, if the REST API is exposed over the network, any remote attacker with valid, low-privileged credentials can potentially exploit the issue by calling the affected endpoint.

Yes. The attacker must first authenticate as a valid user, but they do not need administrative privileges; a limited-permission account is sufficient if it can reach the export endpoint.

Apply strict, role-based authorization checks to the device account export endpoint and any similar administrative APIs, using a centralized access control mechanism that enforces deny-by-default behavior for sensitive operations.

Design and implement a uniform access control layer for all APIs, define clear role and permission models, write tests that verify authorization behavior for sensitive endpoints, and regularly review logs and code for endpoints that accept any authenticated user without verifying their privileges.

Find out what's already
exploitable in your codebase.