{
  "id": "CVE-2026-102509",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-102509",
  "published_at": "2026-09-30T08:00:27.709Z",
  "title": "Apache PLC4X, Apache PLC4X: Pre-authentication resource exhaustion in the OPC UA driver and the Java SPI parser",
  "vendor": "Apache Software Foundation",
  "product": "Apache PLC4X",
  "cvss": {
    "score": 8.7,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "Memory Allocation with Excessive Size Value, Allocation of Resources Without Limits, and Uncontrolled Recursion in the Java implementation of Apache PLC4X (PLC4J) allow a malicious or impersonated device to exhaust the memory or stack of the client application, causing a denial of service.\n\nIn the OPC UA driver these defects are reachable before authentication: the offending data is parsed while the secure channel and session are being established, before the server's identity has been bound to it. Configuring a trusted server therefore does not prevent exploitation by an attacker who can \nimpersonate it.\n\nThe individual defects are:\n- Length-prefixed byte strings are allocated at the size claimed on the wire before the length is checked against the data actually received (0.10.0 through 0.13.1).\n- Array fields in generated protocol parsers pre-allocate a list with the element count claimed on the wire, allowing a single count field to trigger a multi-gigabyte allocation. This parser is shared by all PLC4J drivers; the OPC UA driver is the verified pre-authentication path (0.10.0 through 0.13.1).\n- The OPC UA driver accumulates message chunks without enforcing the negotiated maximum chunk count and message size (0.12.0 through 0.13.1).\n- The OPC UA driver pre-allocates collections using element counts received from the server (0.10.0 through 0.13.1).\n- Recursive protocol types are parsed without a nesting-depth limit. The same defect in the Go implementation is covered by  CVE-2026-102510 https://cveprocess.apache.org/cve5/CVE-2026-102510 .\n\nThis issue affects Apache PLC4X: from 0.10.0 before 1.0.0.\n\nUsers are recommended to upgrade to version 1.0.0, which fixes the issue.",
  "cwe": "CWE-789",
  "cvss_by_source": {
    "cna": 8.7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Apache Software Foundation",
        "product": "Apache PLC4X",
        "ranges": [
          "\u003e= 0.10.0, \u003c 1.0.0"
        ],
        "fixed_in": [
          "1.0.0"
        ]
      },
      {
        "vendor": "Apache Software Foundation",
        "product": "Apache PLC4X",
        "ranges": [
          "\u003e= 0.10.0, \u003c 1.0.0"
        ],
        "fixed_in": [
          "1.0.0"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Apache PLC4X to 1.0.0 or later.",
      "Upgrade Apache PLC4X to 1.0.0 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://lists.apache.org/thread.html/qngc85qhnlj7kpk3z58z0xlxhz2tn6gp"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
