ABB My Control System 26.6 Fixes Temporary-File Exhaustion
Tech GuruQuick Answer
ABB published 7PAA025438 for My Control System 26.4 and 26.5. Move eligible deployments to 26.6, perform the documented one-time cleanup, and use the authority's recovery procedure for Edgenius systems that cannot yet upgrade.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory My Control System nodes, deployment type, version, disk utilization, conversion activity, and Edgenius OS level; update eligible systems to 26.6; perform the documented cleanup only during a safe window; and monitor storage and service health.
Last verified: 2026-10-15 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | ABB My Control System 26.4 and 26.5 on Windows or Edgenius |
|---|---|
| Advisory | 7PAA025438 |
| CVE | CVE-2026-17525 |
| Authoritative release date | 2026-10-15 00:30:00 UTC |
| Authority revision date | 2026-10-15 00:30:00 UTC |
| Affected versions | My Control System 26.4 and 26.5; network exploitation requires access to an affected node and a crafted message. ABB reported no exploitation at publication. |
| Fixed version | My Control System 26.6 for eligible deployments; use ABB's documented Windows or Edgenius cleanup procedure until an Edgenius OS upgrade path is available |
| CVSS base score | 5.2 (CVSS v3.1) |
| CVSS severity | Medium |
| Exploitation status | ABB had not received reports of exploitation when it issued the advisory.; no exploitation claim is inferred. |
What Changed
ABB says incomplete cleanup after XML conversion can exhaust disk space and stop or make a node inaccessible; 26.6 deletes generated temporary files after successful conversion.
What To Validate Now
- Inventory. Locate ABB My Control System 26.4 and 26.5 on Windows or Edgenius deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: My Control System 26.4 and 26.5; network exploitation requires access to an affected node and a crafted message. ABB reported no exploitation at publication. Do not infer applicability from product family or severity alone.
- Remediate. Apply My Control System 26.6 for eligible deployments; use ABB's documented Windows or Edgenius cleanup procedure until an Edgenius OS upgrade path is available 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
ABB says the Edgenius container restart is a recovery measure, not prevention, and should be run only when no analysis is in progress. Confirm the supported OS upgrade path before attempting 26.6. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.
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.
