CVE-2025-14510 ABB CVE debrief

Who should care

OT/ICS security teams, ABB Ability OPTIMAX administrators, and identity/access management owners responsible for deployments that use Azure Active Directory SSO—especially environments still running 6.1, 6.2, or older 6.3/6.4 builds.

Technical summary

The advisory describes a network-reachable authentication bypass affecting OPTIMAX when Azure Active Directory SSO is enabled. ABB lists three exploitation preconditions: the system must be integrated with Azure AD, the attacker must have a network communication channel to OPTIMAX, and the attacker must know a valid non-default username on the system. The published CVSS vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating potentially severe impact if the vulnerable path is reachable.

Defensive priority

High. Prioritize remediation on any OPTIMAX instance that uses Azure AD SSO, because successful abuse can defeat user authentication and the score reflects high confidentiality, integrity, and availability impact.

Recommended defensive actions

• Inventory and confirm which OPTIMAX systems use Azure Active Directory SSO.
• Identify installed versions and compare them with ABB's fixed releases, 6.3.1-251120 and 6.4.1-251120 or later.
• Apply vendor updates as soon as feasible; for older 6.3/6.4 installations, follow ABB's guidance to update the operating system, and for unsupported 6.1/6.2 systems contact ABB for a migration path.
• Limit network reachability to OPTIMAX and keep OT access segmented while remediation is pending.
• Review authentication and access logs for unusual or unexpected successful logins on affected systems.
• Follow ABB and CISA industrial control system hardening guidance for general security recommendations.

Evidence notes

Based on CISA CSAF ICSA-26-120-04 republishing ABB PSIRT advisory 9AKK108472A1331. The source explicitly states the issue is corrected in ABB Ability OPTIMAX 6.3.1-251120 and 6.4.1-251120 or later, and that exploitation requires Azure AD integration, network access, and knowledge of a valid username. No KEV entry was provided in the supplied data.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.