9AKK108472A1331
Vulnerability from csaf_abb - Published: 2026-01-16 00:30 - Updated: 2026-01-16 00:30Summary
ABB Ability™ OPTIMAX® Authentication Bypass in Single-Sign On with Azure Active Directory
Notes
Summary
ABB became aware of severe vulnerability in the products versions listed as affected in the advisory, if the optional integration with Azure Active Directory for Single-Sign On is enabled. We have not received any reports of this vulnerability being exploited.
An attacker who successfully exploits this vulnerability could bypass user authentication and potentially cause the product to:
- Shutdown the system,
- Modify the configuration of the system,
- Install and run arbitrary code
Support
For additional instructions and support please contact your local ABB service organization. For contact information, see www.abb.com/contactcenters.
Information about ABB’s cyber security program and capabilities can be found at www.abb.com/cybersecurity.
Notice
The information in this document is subject to change without notice, and should not be construed as a commitment by ABB.
ABB provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall ABB or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if ABB or its suppliers have been advised of the possibility of such damages.
This document and parts hereof must not be reproduced or copied without written permission from ABB, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.
All rights to registrations and trademarks reside with their respective owners.
General security recommendations
For any installation of software-related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:
- Isolate special purpose networks (e.g. for automation systems) and remote devices behind fire-walls and separate them from any general-purpose network (e.g. office or home networks).
- Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.
- Never connect programming software or computers containing programming software to any network other than the network for the devices that it is intended for.
- Scan all data imported into your environment before use to detect potential malware infections.
- Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.
- Ensure all nodes are always up to date in terms of installed software, operating system, and firmware patches as well as anti-virus and firewall.
- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.
Purpose
ABB has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.
When a potential product vulnerability is identified or reported, ABB immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations.
The resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If ABB is aware of any specific threats, it will be clearly mentioned in the communication.
The publication of this Cyber Security Advisory is an example of ABB’s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.
Frequently Asked Questions
What causes the vulnerability?
- The vulnerability is caused by the possibility to inject code in the authentication script responsible for integration with Azure Active Directory.
What is ABB OPTIMAX?
- OPTIMAX is a software suite that delivers energy management and optimization for energy, emissions, and processes. It provides coordinated control of multiple assets targeting energy efficiency and decarbonization. OPTIMAX is an optimization environment for solving all types of energy management and optimization challenges that industrial enterprises and energy provider face.
What might an attacker use the vulnerability to do?
- An attacker who successfully exploited this vulnerability could run arbitrary code on OPTIMAX and modify the configuration of the system.
How could an attacker exploit the vulnerability?
- An attacker could try to exploit the vulnerability by creating a specially crafted message and sending the message to an affected OPTIMAX system. This would require that the attacker has access to the system
network, by connecting to the network either directly or through a wrongly configured or penetrated firewall, or that he installs malicious software on a system node or otherwise infects the network with malicious software. Recommended practices help mitigate such attacks, see section Mitigating Factors above
Could the vulnerability be exploited remotely?
- Yes, an attacker who has network access to an affected system node could exploit this vulnerability. Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed.
What does the update do?
- The update removes the vulnerability by preventing injection vectors in the authentication script.
When this security advisory was issued, had this vulnerability been publicly disclosed?
- No, ABB discovered this vulnerability through internal testing.
When this security advisory was issued, had ABB received any reports that this vulnerability was being exploited?
- No, ABB had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued.
{
"document": {
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "ABB became aware of severe vulnerability in the products versions listed as affected in the advisory, if the optional integration with Azure Active Directory for Single-Sign On is enabled. We have not received any reports of this vulnerability being exploited.\n\nAn attacker who successfully exploits this vulnerability could bypass user authentication and potentially cause the product to:\n- Shutdown the system,\n- Modify the configuration of the system,\n- Install and run arbitrary code",
"title": "Summary"
},
{
"category": "other",
"text": "For additional instructions and support please contact your local ABB service organization. For contact information, see www.abb.com/contactcenters.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.\n",
"title": "Support"
},
{
"category": "legal_disclaimer",
"text": "The information in this document is subject to change without notice, and should not be construed as a commitment by ABB.\n\nABB provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall ABB or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if ABB or its suppliers have been advised of the possibility of such damages.\n\nThis document and parts hereof must not be reproduced or copied without written permission from ABB, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.\n\nAll rights to registrations and trademarks reside with their respective owners.\n",
"title": "Notice"
},
{
"category": "other",
"text": "For any installation of software-related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:\n\n- Isolate special purpose networks (e.g. for automation systems) and remote devices behind fire-walls and separate them from any general-purpose network (e.g. office or home networks).\n- Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n- Never connect programming software or computers containing programming software to any network other than the network for the devices that it is intended for.\n- Scan all data imported into your environment before use to detect potential malware infections.\n- Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.\n- Ensure all nodes are always up to date in terms of installed software, operating system, and firmware patches as well as anti-virus and firewall.\n- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.",
"title": "General security recommendations"
},
{
"category": "other",
"text": "ABB has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.\n\nWhen a potential product vulnerability is identified or reported, ABB immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations.\n\nThe resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If ABB is aware of any specific threats, it will be clearly mentioned in the communication.\n\nThe publication of this Cyber Security Advisory is an example of ABB\u2019s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.",
"title": "Purpose"
},
{
"category": "faq",
"text": "What causes the vulnerability?\n- The vulnerability is caused by the possibility to inject code in the authentication script responsible for integration with Azure Active Directory.\n\nWhat is ABB OPTIMAX?\n- OPTIMAX is a software suite that delivers energy management and optimization for energy, emissions, and processes. It provides coordinated control of multiple assets targeting energy efficiency and decarbonization. OPTIMAX is an optimization environment for solving all types of energy management and optimization challenges that industrial enterprises and energy provider face.\n\nWhat might an attacker use the vulnerability to do?\n- An attacker who successfully exploited this vulnerability could run arbitrary code on OPTIMAX and modify the configuration of the system.\n\nHow could an attacker exploit the vulnerability?\n- An attacker could try to exploit the vulnerability by creating a specially crafted message and sending the message to an affected OPTIMAX system. This would require that the attacker has access to the system \nnetwork, by connecting to the network either directly or through a wrongly configured or penetrated firewall, or that he installs malicious software on a system node or otherwise infects the network with malicious software. Recommended practices help mitigate such attacks, see section Mitigating Factors above\n\nCould the vulnerability be exploited remotely? \n- Yes, an attacker who has network access to an affected system node could exploit this vulnerability. Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed. \n\nWhat does the update do?\n- The update removes the vulnerability by preventing injection vectors in the authentication script.\n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n- No, ABB discovered this vulnerability through internal testing.\n\nWhen this security advisory was issued, had ABB received any reports that this vulnerability was being exploited?\n- No, ABB had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued.",
"title": "Frequently Asked Questions"
}
],
"publisher": {
"category": "vendor",
"name": "ABB PSIRT",
"namespace": "https://www.abb.com/global/en/company/about/cybersecurity/alerts-and-notifications"
},
"references": [
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - PDF Version ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=9AKK108472A1331\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - CSAF Version ",
"url": "https://psirt.abb.com/csaf/2026/9akk108472a1331.json"
},
{
"summary": "9AKK108472A0435 - OPTIMAX OS Update don_osupdate_v6.4.1-20251120 ",
"url": "https://library.abb.com/d/9AKK108472A0435"
},
{
"summary": "9AKK108472A0437 - OPTIMAX OS Update don_osupdate_v6.3.1-20251120 ",
"url": "https://library.abb.com/d/9AKK108472A0437"
}
],
"title": "ABB Ability\u2122 OPTIMAX\u00ae Authentication Bypass in Single-Sign On with Azure Active Directory",
"tracking": {
"current_release_date": "2026-01-16T00:30:00.000Z",
"generator": {
"date": "2026-01-16T12:21:06.565Z",
"engine": {
"name": "Secvisogram",
"version": "2.5.42"
}
},
"id": "9AKK108472A1331",
"initial_release_date": "2026-01-16T00:30:00.000Z",
"revision_history": [
{
"date": "2026-01-16T00:30:00.000Z",
"legacy_version": "A",
"number": "1",
"summary": "Initial version."
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "vers:all/*",
"product": {
"name": "ABB Ability OPTIMAX 6.1 vers:all/*",
"product_id": "AV1"
}
}
],
"category": "product_name",
"name": "6.1"
},
{
"branches": [
{
"category": "product_version_range",
"name": "vers:all/*",
"product": {
"name": "ABB Ability OPTIMAX 6.2 vers:all/*",
"product_id": "AV2"
}
}
],
"category": "product_name",
"name": "6.2"
},
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c6.3.1-251120",
"product": {
"name": "ABB Ability OPTIMAX 6.3 \u003c6.3.1-251120",
"product_id": "AV3"
}
},
{
"category": "product_version",
"name": "6.3.1-251120",
"product": {
"name": "ABB Ability OPTIMAX 6.3 6.3.1-251120",
"product_id": "FX1"
}
}
],
"category": "product_name",
"name": "6.3"
},
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c6.4.1-251120",
"product": {
"name": "ABB Ability OPTIMAX 6.4 \u003c6.4.1-251120",
"product_id": "AV4"
}
},
{
"category": "product_version",
"name": "6.4.1-251120",
"product": {
"name": "ABB Ability OPTIMAX 6.4 6.4.1-251120",
"product_id": "FX2"
}
}
],
"category": "product_name",
"name": "6.4"
}
],
"category": "product_family",
"name": "Ability OPTIMAX"
}
],
"category": "vendor",
"name": "ABB"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-14510",
"cwe": {
"id": "CWE-303",
"name": "Incorrect Implementation of Authentication Algorithm"
},
"notes": [
{
"category": "description",
"text": "The vulnerability allows an attacker to bypass user authentication on OPTIMAX installations that make use of the Azure Active Directory Single-Sign On integration.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1",
"FX2"
],
"known_affected": [
"AV1",
"AV2",
"AV3",
"AV4"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2025-14510",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-14510"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The problem is corrected in the following product versions:\n- ABB Ability OPTIMAX v6.4.1-251120 (see References 9AKK108472A0435) or later\n- ABB Ability OPTIMAX v6.3.1-251120 (see References 9AKK108472A0437) or later\n\nABB recommends that customers using earlier versions of OPTIMAX v6.4 and OPTIMAX v6.3 apply an update of the operating system at earliest convenience. Customers still using the meanwhile unsupported OPTIMAX v6.2 or v6.1 shall contact ABB to identify the right way forward.",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4"
]
},
{
"category": "mitigation",
"details": "Exploitation requires three preconditions:\n- OPTIMAX is configured to integrate with Azure Active Directory,\n- An attacker has a network communication channel with OPTIMAX,\n- An attacker knows a valid username on the OPTIMAX system other than the default username.\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 6.5,
"environmentalSeverity": "MEDIUM",
"exploitCodeMaturity": "UNPROVEN",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"remediationLevel": "OFFICIAL_FIX",
"reportConfidence": "UNKNOWN",
"scope": "UNCHANGED",
"temporalScore": 6.5,
"temporalSeverity": "MEDIUM",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:U",
"version": "3.1"
},
"products": [
"AV1",
"AV2",
"AV3",
"AV4"
]
}
],
"title": "CVE-2025-14510"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…