7PAA026271

Vulnerability from csaf_abb - Published: 2026-10-22 00:30 - Updated: 2026-10-22 00:30
Summary
ABB Ability Edgenius | Missing Authentication in Edgenius AuthDB
Notes
Summary: ABB identified a critical vulnerability present in ABB Ability Edgenius versions 3.2.3.0 and below. We have not received any reports of this vulnerability being exploited. This issue may allow unauthorized manipulation of the edge authentication database if successfully exploited. ABB has developed and released a corrective update that resolves this vulnerability and enhances the security posture of the affected system.
General security recommendations: Control systems and the control network are exposed to cyber threats. To minimize these risks, the protective measures and best practices listed below are available in addition to other measures. ABB strongly recommends system integrators and asset owners to implement the measures they consider appropriate for their control system environment: - Place control systems in a dedicated control network containing control systems only. - Locate control networks and systems behind firewalls and separate them from any other networks like business networks and the Internet. - Block inbound Internet traffic destined for control networks and systems. Remote access solutions used to access control systems should be located outside the control network and appropriately secured. - Limit outbound Internet traffic originating from control systems and control networks as much as possible. Where Internet connectivity is required, restrict firewall rules to the source addresses, destination addresses, services, and ports necessary for normal control operation. - Limit exposure of control networks and systems to internal networks. Configure firewall rules to permit only the communication required for normal control operation. - Restrict access to database services. Databases supporting control system or Edge Service functionality should be accessible only by authorized systems and services that require access for normal operation. Database services should not be exposed to untrusted networks. - Create strict firewall rules to filter malicious network traffic targeting control system vulnerabilities ("exploit traffic"). Exploit traffic may use network communication features like source routing, IP fragmentation and/or IP tunneling. If such features are not required for normal control operation, block them on your firewall. - If supported by your firewall, apply additional filters to allow traffic which provide protection for control networks/systems. Such filters are provided by advanced firewall features like Application Control and Anti-Virus. - Use Intrusion Detection Systems (IDS) or Intrusion Preventions Systems (IPS) to detect/block control system-specific exploit traffic. Consider using IPS rules protecting against control system exploits. - When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Please ensure that VPN solutions are updated to the most current version available. - In case you want to filter internal control network traffic, consider using solutions supporting Intra LAN traffic control like VLAN access control lists. - Harden your control systems by enabling only the ports, services and software required for normal control operation. Disable all other ports and disable/uninstall all other services and software. - If possible, limit the permissions of user accounts, software processes and devices to the permissions required for normal control operation. - Use trusted, patched software and malware protection solutions. Interact with trusted web sites and trusted email attachments only. - 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. Protect control systems from physical access by unauthorized personnel e.g. by placing them in locked switch cabinets.
Support: For additional instructions and support please contact your local ABB service organization. For contact information, see https://new.abb.com/contact-centers. Information about ABB’s cyber security program and capabilities can be found at https://www.abb.com/global/en/company/about/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 hard-ware 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.
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 (e.g. ICS-CERT). 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 is the Scope of the vulnerability? - The vulnerability affects the platform authentication layer and could allow unauthorized modification of authentication data. This could affect user access controls, dependent edge services, and overall platform integrity. What causes this vulnerability? - The vulnerability is caused by missing authentication between internal functions within the product. What is Edge AuthDB? - Edge AuthDB is the internal service which holds the persistence of authorization information for Edgenius. What might an attacker use the vulnerability to do? - A successful attacker could modify authentication database records. The Edge Auth API could then use the modified data to validate user authorization, which could affect how applications determine user permissions. How could an attacker exploit this vulnerability? - An attacker with local Linux access to the Edgenius node could try to exploit the vulnerability by accessing the affected service and modifying records without using the API Could the vulnerabilities be exploited remotely? - No, to exploit this vulnerability an attacker would need to have local access to an affected system node. Can functional safety be affected by an exploit of this vulnerability? - No, the functional safety will not be affected by an exploit of this vulnerability. What does the update do? - The update restricts internal access to the affected service so that only the API can reach it and furthermore implements authentication and authorization in the affected service. When this security advisory was issued, had this vulnerability been publicly disclosed? - No, ABB received information about 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.
CVE-2026-13599

ABB Ability Edgenius | Missing Authentication in Edgenius AuthDB ABB identified a vulnerability in the Edge AuthDB component in the affected product versions listed as affected in the advisory. An attacker with the required local access could manipulate database data, disrupt related edge services, make the node unavailable or inaccessible, or gain unauthorized control of the system.

7.8 (High)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:F/RL:O/RC:C/CR:H/IR:M/AR:H/MAV:L/MAC:H/MPR:L/MUI:N/MS:C/MC:H/MI:H/MA:H
CWE-306 - Missing Authentication for Critical Function
Affected products
Product Identifier Version Remediation
ABB Ability Edgenius 3.2.4.1
ABB / Ability Edgenius
 3.2.4.1
Product Identifier Version Remediation
ABB Ability Edgenius <=3.2.3.0
ABB / Ability Edgenius
 <=3.2.3.0
Workaround
Mitigation
Vendor Fix
References
To clipboard 

{
  "document": {
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "tlp": {
        "label": "WHITE"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "ABB identified a critical vulnerability present in ABB Ability Edgenius versions 3.2.3.0 and below. We have not received any reports of this vulnerability being exploited. \n\nThis issue may allow unauthorized manipulation of the edge authentication database if successfully exploited. \n\nABB has developed and released a corrective update that resolves this vulnerability and enhances the security posture of the affected system. ",
        "title": "Summary"
      },
      {
        "category": "other",
        "text": "Control systems and the control network are exposed to cyber threats. To minimize these risks, the protective measures and best practices listed below are available in addition to other measures. ABB strongly recommends system integrators and asset owners to implement the measures they consider appropriate for their control system environment: \n\n- Place control systems in a dedicated control network containing control systems only. \n- Locate control networks and systems behind firewalls and separate them from any other networks like business networks and the Internet. \n- Block inbound Internet traffic destined for control networks and systems. Remote access solutions used to access control systems should be located outside the control network and appropriately secured. \n- Limit outbound Internet traffic originating from control systems and control networks as much as possible. Where Internet connectivity is required, restrict firewall rules to the source addresses, destination addresses, services, and ports necessary for normal control operation. \n- Limit exposure of control networks and systems to internal networks. Configure firewall rules to permit only the communication required for normal control operation. \n- Restrict access to database services. Databases supporting control system or Edge Service functionality should be accessible only by authorized systems and services that require access for normal operation. Database services should not be exposed to untrusted networks. \n- Create strict firewall rules to filter malicious network traffic targeting control system vulnerabilities (\"exploit traffic\"). Exploit traffic may use network communication features like source routing, IP fragmentation and/or IP tunneling. If such features are not required for normal control operation, block them on your firewall. \n- If supported by your firewall, apply additional filters to allow traffic which provide protection for control networks/systems. Such filters are provided by advanced firewall features like Application Control and Anti-Virus. \n- Use Intrusion Detection Systems (IDS) or Intrusion Preventions Systems (IPS) to detect/block control system-specific exploit traffic. Consider using IPS rules protecting against control system \nexploits. \n- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Please ensure that VPN solutions are updated to the most current version available. \n- In case you want to filter internal control network traffic, consider using solutions supporting Intra LAN traffic control like VLAN access control lists. \n- Harden your control systems by enabling only the ports, services and software required for normal control operation. Disable all other ports and disable/uninstall all other services and software. \n- If possible, limit the permissions of user accounts, software processes and devices to the permissions required for normal control operation. \n- Use trusted, patched software and malware protection solutions. Interact with trusted web sites and trusted email attachments only.\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\nProtect control systems from physical access by unauthorized personnel e.g. by placing them in locked switch cabinets.",
        "title": "General security recommendations"
      },
      {
        "category": "other",
        "text": "For additional instructions and support please contact your local ABB service organization. For contact information, see https://new.abb.com/contact-centers.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at https://www.abb.com/global/en/company/about/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 hard-ware 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": "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 (e.g. ICS-CERT).\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 is the Scope of the vulnerability?\n- The vulnerability affects the platform authentication layer and could allow unauthorized modification of authentication data. This could affect user access controls, dependent edge services, and overall platform integrity.\n\nWhat causes this vulnerability?\n- The vulnerability is caused by missing authentication between internal functions within the product.\n\nWhat is Edge AuthDB?\n- Edge AuthDB is the internal service which holds the persistence of authorization information for Edgenius.\n\nWhat might an attacker use the vulnerability to do?\n- A successful attacker could modify authentication database records. The Edge Auth API could then use the modified data to validate user authorization, which could affect how applications determine user permissions.\n\nHow could an attacker exploit this vulnerability?\n- An attacker with local Linux access to the Edgenius node could try to exploit the vulnerability by accessing the affected service and modifying records without using the API\n\nCould the vulnerabilities be exploited remotely?\n- No, to exploit this vulnerability an attacker would need to have local access to an affected system node.\n\nCan functional safety be affected by an exploit of this vulnerability?\n- No, the functional safety will not be affected by an exploit of this vulnerability.\n\nWhat does the update do?\n- The update restricts internal access to the affected service so that only the API can reach it and furthermore implements authentication and authorization in the affected service.\n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n- No, ABB received information about 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=7PAA026271\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
      },
      {
        "category": "self",
        "summary": "ABB CYBERSECURITY ADVISORY - CSAF version ",
        "url": "https://psirt.abb.com/csaf/2026/7paa026271.json"
      },
      {
        "summary": "Technical Description ABB Ability Edgenius Missing Authentication in Edgenius AuthDB (7PAA025722)",
        "url": "https://search.abb.com/library/Download.aspx?DocumentID=7PAA025722\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
      }
    ],
    "title": "ABB Ability Edgenius | Missing Authentication in  Edgenius AuthDB ",
    "tracking": {
      "current_release_date": "2026-10-22T00:30:00.000Z",
      "generator": {
        "date": "2026-10-22T17:09:14.479Z",
        "engine": {
          "name": "Secvisogram",
          "version": "2.6.16"
        }
      },
      "id": "7PAA026271",
      "initial_release_date": "2026-10-22T00:30:00.000Z",
      "revision_history": [
        {
          "date": "2026-10-22T00:30:00.000Z",
          "legacy_version": "A",
          "number": "1",
          "summary": "Initial version."
        }
      ],
      "status": "final",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c=3.2.3.0",
                "product": {
                  "name": "ABB Ability Edgenius \u003c=3.2.3.0",
                  "product_id": "AV1"
                }
              },
              {
                "category": "product_version",
                "name": "3.2.4.1 ",
                "product": {
                  "name": "ABB Ability Edgenius 3.2.4.1 ",
                  "product_id": "FX1"
                }
              }
            ],
            "category": "product_name",
            "name": "Ability Edgenius"
          }
        ],
        "category": "vendor",
        "name": "ABB"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-13599",
      "cwe": {
        "id": "CWE-306",
        "name": "Missing Authentication for Critical Function"
      },
      "notes": [
        {
          "category": "description",
          "text": "ABB Ability Edgenius | Missing Authentication in Edgenius AuthDB\n\nABB identified a vulnerability in the Edge AuthDB component in the affected product versions listed as affected in the advisory. An attacker with the required local access could manipulate database data, disrupt related edge services, make the node unavailable or inaccessible, or gain unauthorized control of the system.  ",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "fixed": [
          "FX1"
        ],
        "known_affected": [
          "AV1"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD -CVE-2026-13599",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-13599"
        }
      ],
      "remediations": [
        {
          "category": "workaround",
          "details": "Workarounds are specific measures that a user can take to help block an attack, for example, temporarily disabling the vulnerable feature may remove exposure with well-known impact on functionality.\n\nFor brownfield customers, ABB provides a Kubernetes network policy that restricts access to Edge Authentication Database (AuthDB) to the authorized services required for normal operation of an already deployed and configured system. \n\nFor implementation details, refer to Technical Description-ABB Ability Edgenius Missing Authentication in Edgenius AuthDB.docx (7PAA025722) listed in the reference section, distributed separately.\n",
          "product_ids": [
            "AV1"
          ]
        },
        {
          "category": "mitigation",
          "details": "The following conditions reduce the likelihood of successful exploitation. For additional guidance, see General security recommendations\n- Ensure systems are accessible only from trusted networks \n- Restrict access to edge nodes using firewall rules and network segmentation \n- Maintain up-to-date patches for OS, firmware, and dependent components \n- Interact only with trusted applications, software packages, and email attachments \n- Protect systems from unauthorized physical access\n",
          "product_ids": [
            "AV1"
          ]
        },
        {
          "category": "vendor_fix",
          "details": "ABB fixed this vulnerability in ABB Ability Edgenius version 3.2.4.1 and later. Customers should upgrade to version 3.2.4.1 or later as soon as possible",
          "product_ids": [
            "AV1"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "HIGH",
            "attackVector": "LOCAL",
            "availabilityImpact": "HIGH",
            "availabilityRequirement": "HIGH",
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "confidentialityRequirement": "HIGH",
            "environmentalScore": 7.3,
            "environmentalSeverity": "HIGH",
            "exploitCodeMaturity": "FUNCTIONAL",
            "integrityImpact": "HIGH",
            "integrityRequirement": "MEDIUM",
            "modifiedAttackComplexity": "HIGH",
            "modifiedAttackVector": "LOCAL",
            "modifiedAvailabilityImpact": "HIGH",
            "modifiedConfidentialityImpact": "HIGH",
            "modifiedIntegrityImpact": "HIGH",
            "modifiedPrivilegesRequired": "LOW",
            "modifiedScope": "CHANGED",
            "modifiedUserInteraction": "NONE",
            "privilegesRequired": "LOW",
            "remediationLevel": "OFFICIAL_FIX",
            "reportConfidence": "CONFIRMED",
            "scope": "CHANGED",
            "temporalScore": 7.2,
            "temporalSeverity": "HIGH",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:F/RL:O/RC:C/CR:H/IR:M/AR:H/MAV:L/MAC:H/MPR:L/MUI:N/MS:C/MC:H/MI:H/MA:H",
            "version": "3.1"
          },
          "products": [
            "AV1"
          ]
        }
      ],
      "title": "CVE-2026-13599"
    }
  ]
}



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

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.