ABB PCM600 Scheduler Service Requires Privilege-Escalation Workaround
Tech GuruQuick Answer
The authority published 2NGA003170 for ABB Protection and Control IED Manager PCM600 through version 2.14. ABB is aware of a reported vulnerability in ABB Protection and Control IED Manager (PCM600). A local authenticated user belonging to the PCM600 user group may be able to modify the configuration of a Windows service running with SYSTEM privileges. Successful exploitation could allow an attacker to execute arbitrary commands with elevated privileges on the affected workstation. Note: This document references the ABBPCMSchedulerService_v214 component as implemented in PCM600 version 2.14. However, the described issue is not version-specific and applies equally to the corresponding component in other supported versions of PCM600. A vulnerability exists in the Scheduler Service installed with PCM600. The service executes under the LocalSystem account while permissions are granted to standard PCM600 users through membership in the local users group. An attacker with local access and valid user credentials may exploit this vulnerability to elevate privileges and obtain control of the affected host. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory ABB Protection and Control IED Manager PCM600 through version 2.14, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-28 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | ABB Protection and Control IED Manager PCM600 through version 2.14 |
|---|---|
| Advisory | 2NGA003170 |
| CVE | CVE-2026-15952 |
| Authoritative release date | 2026-09-28 00:30:00 UTC (ABB CSAF initial release); added to the ABB CSAF feed at 2026-09-28 12:00:00 UTC |
| Authority revision date | 2026-09-28 00:30:00.000 UTC |
| Affected versions | Supported ABB PCM600 versions through 2.14 with the Scheduler Service configured to run as LocalSystem while granting service-control permissions to PCM600 users. |
| Fixed version | No fixed release stated; configure the applicable ABBPCMSchedulerService to run as the same Windows account used for PCM600, following ABB's documented workaround |
| CVSS base score | 6.4 (CVSS v3.1) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
ABB is aware of a reported vulnerability in ABB Protection and Control IED Manager (PCM600). A local authenticated user belonging to the PCM600 user group may be able to modify the configuration of a Windows service running with SYSTEM privileges. Successful exploitation could allow an attacker to execute arbitrary commands with elevated privileges on the affected workstation. Note: This document references the ABBPCMSchedulerService_v214 component as implemented in PCM600 version 2.14. However, the described issue is not version-specific and applies equally to the corresponding component in other supported versions of PCM600. A vulnerability exists in the Scheduler Service installed with PCM600. The service executes under the LocalSystem account while permissions are granted to standard PCM600 users through membership in the local users group. An attacker with local access and valid user credentials may exploit this vulnerability to elevate privileges and obtain control of the affected host.
What To Validate Now
- Inventory. Locate ABB Protection and Control IED Manager PCM600 through version 2.14 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Supported ABB PCM600 versions through 2.14 with the Scheduler Service configured to run as LocalSystem while granting service-control permissions to PCM600 users. Do not infer applicability from product family or severity alone.
- Remediate. Apply No fixed release stated; configure the applicable ABBPCMSchedulerService to run as the same Windows account used for PCM600, following ABB's documented workaround through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
