4JXD000118

Vulnerability from csaf_abb - Published: 2026-11-11 00:30 - Updated: 2026-11-11 00:30
Summary
ABB Ability™ OPTIMAX® Node2Shell
Notes
Summary: An update is available that resolves a publicly reported vulnerability in the product versions listed as affected in the advisory. An attacker who successfully exploited this vulnerability could cause the product to insert 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 firewalls 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 programing 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 a buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. The Brotli library is present is in the DON-Runtime and Node-Red components in the products ABB Ability™ OPTIMAX® 6.4.1, and ABB Ability™ OPTIMAX®, 6.5.0. What is ABB Ability™ 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 providers face What might an attacker use the vulnerability to do? - An attacker who successfully exploited this vulnerability could run arbitrary code. 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 system node. 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,, if the attacker was previously authenticated in the system. What does the update do? - The update removes the vulnerability by upgrading the Brotli nodejs library library in the ABB Ability™ OPTIMAX® system and OS. When this security advisory was issued, had this vulnerability been publicly disclosed? - Yes, this vulnerability has been publicly disclosed. 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.
CVE-2026-111497

Google Brotli C compression decoder library is deeply bundled into popular software architectures. The flaw allows unauthenticated remote attackers to trigger denial-of-service (DoS) crashes, disclose sensitive memory, or achieve full Remote Code Execution (RCE) under the context of the running application

9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/RL:O/RC:C/CR:M/IR:M/AR:M/MPR:L
CWE-122 - Heap-based Buffer Overflow
Affected products
Product Identifier Version Remediation
ABB ABB Ability™ OPTIMAX® 6.4.1
ABB / ABB Ability™ OPTIMAX®
 6.4.1
Vendor Fix
Workaround
Mitigation
ABB ABB Ability™ OPTIMAX® 6.5.0
ABB / ABB Ability™ OPTIMAX®
 6.5.0
Vendor Fix
Workaround
Mitigation
References
To clipboard 

{
  "document": {
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "\u00a9 Copyright 2026 ABB. All rights reserved.",
      "tlp": {
        "label": "WHITE"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "An update is available that resolves a publicly reported vulnerability in the product versions listed as affected in the advisory.\n\nAn attacker who successfully exploited this vulnerability could cause the product to insert 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.",
        "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.",
        "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 firewalls 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 programing 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\u0027s 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 a buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. The Brotli library is present is in the DON-Runtime and Node-Red components in the products ABB Ability\u2122 OPTIMAX\u00ae 6.4.1, and ABB Ability\u2122 OPTIMAX\u00ae, 6.5.0.\n\nWhat is ABB Ability\u2122 OPTIMAX\u00ae?\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 providers face\n\nWhat might an attacker use the vulnerability to do?\n- An attacker who successfully exploited this vulnerability could run arbitrary code.\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 system node. 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.\n\nCould the vulnerability be exploited remotely?\n- Yes,, if the attacker was previously authenticated in the system.\n\nWhat does the update do?\n- The update removes the vulnerability by upgrading the Brotli nodejs library library in the ABB Ability\u2122 OPTIMAX\u00ae system and OS.\n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n- Yes, this vulnerability has been publicly disclosed.\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.",
        "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=4JXD000118\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
      },
      {
        "category": "self",
        "summary": "ABB CYBERSECURITY ADVISORY - CSAF Version ",
        "url": "https://psirt.abb.com/csaf/2026/4jxd000118.json"
      }
    ],
    "title": "ABB Ability\u2122 OPTIMAX\u00ae Node2Shell",
    "tracking": {
      "current_release_date": "2026-11-11T00:30:00.000Z",
      "generator": {
        "date": "2026-11-11T17:45:22.142Z",
        "engine": {
          "name": "Secvisogram",
          "version": "2.6.19"
        }
      },
      "id": "4JXD000118",
      "initial_release_date": "2026-11-11T00:30:00.000Z",
      "revision_history": [
        {
          "date": "2026-11-11T00:30:00.000Z",
          "legacy_version": "A",
          "number": "1",
          "summary": "Initial version."
        }
      ],
      "status": "draft",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "6.4.1",
                "product": {
                  "name": "ABB ABB Ability\u2122 OPTIMAX\u00ae 6.4.1",
                  "product_id": "AV1"
                }
              },
              {
                "category": "product_version",
                "name": "6.5.0",
                "product": {
                  "name": "ABB ABB Ability\u2122 OPTIMAX\u00ae 6.5.0",
                  "product_id": "AV2"
                }
              }
            ],
            "category": "product_name",
            "name": "ABB Ability\u2122 OPTIMAX\u00ae"
          }
        ],
        "category": "vendor",
        "name": "ABB"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-111497",
      "cwe": {
        "id": "CWE-122",
        "name": "Heap-based Buffer Overflow"
      },
      "notes": [
        {
          "category": "description",
          "text": "Google Brotli C compression decoder library is deeply bundled into popular software architectures. The flaw allows unauthenticated remote attackers to trigger denial-of-service (DoS) crashes, disclose sensitive memory, or achieve full Remote Code Execution (RCE) under the context of the running application",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "known_affected": [
          "AV1",
          "AV2"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD - CVE-2026-111497",
          "url": "https://nvd.nist.gov/vuln/detail/cve-2026-111497"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product version:\n\n- ABB Ability\u2122 OPTIMAX\u00ae, 6.4.1\n  OS Patch. Optional but recommended (don_osupdate_v6.4.1-release-date)\n  OPTIMAX patch (OPTIMAX_v6.4.1+ release-date.iso)\n\nABB recommends that customers apply the update at earliest convenience.\n\nA technical note will be made available to ABB customers via ABB Library describing the patching instructions.",
          "product_ids": [
            "AV1"
          ]
        },
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product version:\n\n- ABB Ability\u2122 OPTIMAX\u00ae, 6.5.1\n  OS Patch. Optional but recommended (don_osupdate_v6.5.1- release-date)\n  OPTIMAX patch (OPTIMAX_v6.5.1+ release-date.iso)\n\nABB recommends that customers apply the update at earliest convenience.\n\nA technical note will be made available to ABB customers via ABB Library describing the patching instructions.",
          "product_ids": [
            "AV2"
          ]
        },
        {
          "category": "workaround",
          "details": "Besides the official patches there are the following workarounds:\n\n- Configure NGINX more restrictive, see RHSB-2026-015 Out-of-Bounds Write - Google Brotli Decoder (CVE-2026-111497) - \"node2shell\" | Red Hat Customer Portal\n- Just apply the don/runtime image patch.",
          "product_ids": [
            "AV1",
            "AV2"
          ]
        },
        {
          "category": "mitigation",
          "details": "The libbrotli library is present in OPTIMAX at the OS level and in some containerized components.\n\nAt OS level, the libbrotli library is present but not used. Upgrading or deleting the libbrotli library would mitigate the possibility of an unauthorized attack.\n\nExploitation requires the following preconditions:\n- The attacker has a network communication channel with OPTIMAX\n- Successful authentication and sufficient privileges necessary to submit Brotli-compressed requests to the affected endpoint.\n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.",
          "product_ids": [
            "AV1",
            "AV2"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "availabilityRequirement": "MEDIUM",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "confidentialityRequirement": "MEDIUM",
            "environmentalScore": 8.4,
            "environmentalSeverity": "HIGH",
            "exploitCodeMaturity": "NOT_DEFINED",
            "integrityImpact": "HIGH",
            "integrityRequirement": "MEDIUM",
            "modifiedPrivilegesRequired": "LOW",
            "privilegesRequired": "NONE",
            "remediationLevel": "OFFICIAL_FIX",
            "reportConfidence": "CONFIRMED",
            "scope": "UNCHANGED",
            "temporalScore": 9.4,
            "temporalSeverity": "CRITICAL",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/RL:O/RC:C/CR:M/IR:M/AR:M/MPR:L",
            "version": "3.1"
          },
          "products": [
            "AV1",
            "AV2"
          ]
        }
      ],
      "title": "CVE-2026-111497"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.