SA26P015

Vulnerability from csaf_abb - Published: 2026-10-23 00:30 - Updated: 2026-10-23 01:30
Summary
APROL Impact of PHP2Shell
Notes
Summary: B&R is aware of public reports of a vulnerability in the product versions listed as affected in the advisory. An attacker who successfully exploits these vulnerabilities may insert and run arbitrary code on affected devices.
Support: For additional instructions and support please contact your local B&R service organization. For contact information, see https://www.br-automation.com/en/about-us/locations/. 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 B&R. B&R 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 B&R 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 B&R 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 B&R, 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. For more information on recommended practices, please refer to the following documents listed in the reference section: - Defense in Depth for B&R products
Purpose: B&R 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, B&R 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 B&R 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 B&R’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: How could an attacker exploit the vulnerabilities? - An attacker could try to exploit the vulnerabilities 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 vulnerabilities be exploited remotely? - Yes, an attacker who has network access to an affected system node could exploit these vulnerabilities. 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. When this security advisory was issued, had these vulnerabilities been publicly disclosed? - Yes, these vulnerabilities have been publicly disclosed. When this security advisory was issued, had B&R received any reports that these vulnerabilities were being exploited? - No, B&R had not received any information indicating that these vulnerabilities have been exploited in APROL when this security advisory was originally issued.
CVE-2026-109618

PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).

9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C
CWE-1325 - Improperly Controlled Sequential Memory Allocation
Affected products
Product Identifier Version Remediation
B&R Industrial Automation GmbH APROL <=R 4.4-65
B&R Industrial Automation GmbH / APROL
 <=R 4.4-65
Vendor Fix
Mitigation
CVE-2026-109619

PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).

9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C
CWE-1325 - Improperly Controlled Sequential Memory Allocation
Affected products
Known affected 1 product, the same list as for CVE-2026-109618
References
To clipboard 

{
  "document": {
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "tlp": {
        "label": "WHITE"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "B\u0026R is aware of public reports of a vulnerability in the product versions listed as affected in the advisory.\n\nAn attacker who successfully exploits these vulnerabilities may insert and run arbitrary code on affected devices.\n",
        "title": "Summary"
      },
      {
        "category": "other",
        "text": "For additional instructions and support please contact your local B\u0026R service organization. For contact information, see https://www.br-automation.com/en/about-us/locations/.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.\n\n\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 B\u0026R.\n\nB\u0026R 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 B\u0026R 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 B\u0026R 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 B\u0026R, 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\n- Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n\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\n- Scan all data imported into your environment before use to detect potential malware infections.\n\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\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\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.\n\nFor more information on recommended practices, please refer to the following documents listed in the reference section:\n\n- Defense in Depth for B\u0026R products\n",
        "title": "General security recommendations"
      },
      {
        "category": "other",
        "text": "B\u0026R 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, B\u0026R 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 B\u0026R 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 B\u0026R\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": "How could an attacker exploit the vulnerabilities?\n- An attacker could try to exploit the vulnerabilities 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 vulnerabilities be exploited remotely? \n- Yes, an attacker who has network access to an affected system node could exploit these vulnerabilities. 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\nWhen this security advisory was issued, had these vulnerabilities been publicly disclosed?\n- Yes, these vulnerabilities have been publicly disclosed.\n\nWhen this security advisory was issued, had B\u0026R received any reports that these vulnerabilities were being exploited?\n- No, B\u0026R had not received any information indicating that these vulnerabilities have been exploited in APROL when this security advisory was originally issued.\n\n",
        "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": "B\u0026R CYBERSECURITY ADVISORY - PDF Version ",
        "url": "https://br-cws-assets.de-fra-1.linodeobjects.com/SA26P015-7cd6ca9c.pdf"
      },
      {
        "category": "self",
        "summary": "B\u0026R CYBERSECURITY ADVISORY - CSAF Version ",
        "url": "https://psirt.abb.com/csaf/2026/sa26p015.json"
      },
      {
        "summary": "Defense in Depth for B\u0026R products\n",
        "url": "https://www.br-automation.com/fileadmin/Cyber_Security_-_Defense_in_Depth_for_BR_Products-bdd37e82.pdf"
      }
    ],
    "title": "APROL Impact of PHP2Shell",
    "tracking": {
      "current_release_date": "2026-10-23T01:30:00.000Z",
      "generator": {
        "date": "2026-10-23T11:14:47.501Z",
        "engine": {
          "name": "Secvisogram",
          "version": "2.6.16"
        }
      },
      "id": "SA26P015",
      "initial_release_date": "2026-10-23T00:30:00.000Z",
      "revision_history": [
        {
          "date": "2026-10-23T00:30:00.000Z",
          "legacy_version": "A",
          "number": "1",
          "summary": "Initial version."
        },
        {
          "date": "2026-10-23T01:30:00.000Z",
          "number": "2",
          "summary": "Correction in the text"
        }
      ],
      "status": "final",
      "version": "2"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c=R 4.4-65",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH APROL \u003c=R 4.4-65",
                  "product_id": "AV1"
                }
              }
            ],
            "category": "product_name",
            "name": "APROL"
          }
        ],
        "category": "vendor",
        "name": "B\u0026R Industrial Automation GmbH"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-109618",
      "cwe": {
        "id": "CWE-1325",
        "name": "Improperly Controlled Sequential Memory Allocation"
      },
      "notes": [
        {
          "category": "description",
          "text": "PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "known_affected": [
          "AV1"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD - CVE-2026-109618",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109618"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "B\u0026R is actively working on patch versions for affected products. Based on current planning, these are expected to be released on October 26, 2026 (for R 4.4-65) and October 29, 2026 (for R 4.4-01). B\u0026R will up-date this advisory if these dates change.\nAPROL is intended to be operated only in environments with restricted logical and physical access, as described in the product documentation and in \u201cDefense in Depth for B\u0026R products\u201d. Until patches are available and installed, B\u0026R recommends that customers restrict HTTP(S) traffic to the APROL system, particularly from untrusted networks, and implement additional security measures to limit access to the product to trusted personnel. We advise customers to review and validate their current access re-strictions to confirm that logical and physical access controls are configured in line with these recom-mendations. These measures reduce, but may not fully eliminate, the risk of exploitation.\n",
          "product_ids": [
            "AV1"
          ]
        },
        {
          "category": "mitigation",
          "details": "APROL is intended to be operated only in environments with restricted logical and physical access, as described in the product documentation and in \u201cDefense in Depth for B\u0026R products\u201d. Until patches are available and installed, B\u0026R recommends that customers implement additional security measures to limit access to the product to trusted personnel. We advise customers to review and validate their cur-rent access restrictions to confirm that logical and physical access controls are configured in line with these recommendations. These measures reduce, but may not fully eliminate, the risk of exploitation.\nIt is recommended to block any HTTP(S) traffic, particularly from untrusted networks, reaching the APROL system on your connected firewalls.\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
          "product_ids": [
            "AV1"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "environmentalScore": 9.4,
            "environmentalSeverity": "CRITICAL",
            "exploitCodeMaturity": "HIGH",
            "integrityImpact": "HIGH",
            "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/E:H/RL:O/RC:C",
            "version": "3.1"
          },
          "products": [
            "AV1"
          ]
        }
      ],
      "title": "CVE-2026-109618"
    },
    {
      "cve": "CVE-2026-109619",
      "cwe": {
        "id": "CWE-1325",
        "name": "Improperly Controlled Sequential Memory Allocation"
      },
      "notes": [
        {
          "category": "description",
          "text": "PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "known_affected": [
          "AV1"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD - CVE-2026-109619",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109619"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "B\u0026R is actively working on patch versions for affected products. Based on current planning, these are expected to be released on October 26, 2026 (for R 4.4-65) and October 29, 2026 (for R 4.4-01). B\u0026R will up-date this advisory if these dates change.\nAPROL is intended to be operated only in environments with restricted logical and physical access, as described in the product documentation and in \u201cDefense in Depth for B\u0026R products\u201d. Until patches are available and installed, B\u0026R recommends that customers restrict HTTP(S) traffic to the APROL system, particularly from untrusted networks, and implement additional security measures to limit access to the product to trusted personnel. We advise customers to review and validate their current access re-strictions to confirm that logical and physical access controls are configured in line with these recom-mendations. These measures reduce, but may not fully eliminate, the risk of exploitation.\n",
          "product_ids": [
            "AV1"
          ]
        },
        {
          "category": "mitigation",
          "details": "APROL is intended to be operated only in environments with restricted logical and physical access, as described in the product documentation and in \u201cDefense in Depth for B\u0026R products\u201d. Until patches are available and installed, B\u0026R recommends that customers implement additional security measures to limit access to the product to trusted personnel. We advise customers to review and validate their cur-rent access restrictions to confirm that logical and physical access controls are configured in line with these recommendations. These measures reduce, but may not fully eliminate, the risk of exploitation.\nIt is recommended to block any HTTP(S) traffic, particularly from untrusted networks, reaching the APROL system on your connected firewalls.\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
          "product_ids": [
            "AV1"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "environmentalScore": 9.4,
            "environmentalSeverity": "CRITICAL",
            "exploitCodeMaturity": "HIGH",
            "integrityImpact": "HIGH",
            "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/E:H/RL:O/RC:C",
            "version": "3.1"
          },
          "products": [
            "AV1"
          ]
        }
      ],
      "title": "CVE-2026-109619"
    }
  ]
}



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.