{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-102509", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "state": "PUBLISHED", "assignerShortName": "apache", "dateReserved": "2026-09-29T11:41:21.875Z", "datePublished": "2026-09-30T08:00:27.709Z", "dateUpdated": "2026-09-30T14:40:06.881Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "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", "problemTypes": [ { "descriptions": [ { "description": "CWE-789 Memory Allocation with Excessive Size Value. This covers the byte strings (F2), the array counts (F4) and the element counts (f024).", "lang": "en", "cweId": "CWE-789", "type": "CWE" } ] }, { "descriptions": [ { "description": "CWE-770 Allocation of Resources Without Limits or Throttling. This covers the chunk accumulation (F3).", "lang": "en", "cweId": "CWE-770", "type": "CWE" } ] }, { "descriptions": [ { "description": "CWE-674 Uncontrolled Recursion. This covers the nested mspec types (f045).", "lang": "en", "cweId": "CWE-674", "type": "CWE" } ] } ], "source": { "discovery": "EXTERNAL" }, "affected": [ { "vendor": "Apache Software Foundation", "product": "Apache PLC4X", "packageURL": "pkg:maven/org.apache.plc4x/plc4j-spi", "versions": [ { "status": "affected", "version": "0.10.0", "lessThan": "1.0.0", "versionType": "semver" }, { "status": "unaffected", "version": "1.0.0", "versionType": "semver" } ], "defaultStatus": "unaffected", "collectionURL": "https://repo.maven.apache.org/maven2", "packageName": "org.apache.plc4x:plc4j-spi" }, { "vendor": "Apache Software Foundation", "product": "Apache PLC4X", "packageURL": "pkg:maven/org.apache.plc4x/plc4j-driver-opcua", "versions": [ { "status": "affected", "version": "0.10.0", "lessThan": "1.0.0", "versionType": "semver" }, { "status": "unaffected", "version": "1.0.0", "versionType": "semver" } ], "defaultStatus": "unaffected", "collectionURL": "https://repo.maven.apache.org/maven2", "packageName": "org.apache.plc4x:plc4j-driver-opcua" } ], "descriptions": [ { "value": "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.", "lang": "en", "supportingMedia": [ { "type": "text/html", "base64": false, "value": "
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.

In 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 
impersonate it.

The individual defects are:
- 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).
- 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).
- The OPC UA driver accumulates message chunks without enforcing the negotiated maximum chunk count and message size (0.12.0 through 0.13.1).
- The OPC UA driver pre-allocates collections using element counts received from the server (0.10.0 through 0.13.1).
- Recursive protocol types are parsed without a nesting-depth limit. The same defect in the Go implementation is covered by CVE-2026-102510.

This issue affects Apache PLC4X: from 0.10.0 before 1.0.0.

Users are recommended to upgrade to version 1.0.0, which fixes the issue.
" } ] } ], "references": [ { "url": "https://lists.apache.org/thread.html/qngc85qhnlj7kpk3z58z0xlxhz2tn6gp", "tags": [ "vendor-advisory" ] } ], "metrics": [ { "scenarios": [ { "lang": "en", "value": "GENERAL" } ], "format": "CVSS", "cvssV4_0": { "attackVector": "NETWORK", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "userInteraction": "NONE", "vulnConfidentialityImpact": "NONE", "subConfidentialityImpact": "NONE", "vulnIntegrityImpact": "NONE", "subIntegrityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "subAvailabilityImpact": "NONE", "exploitMaturity": "NOT_DEFINED", "Safety": "NOT_DEFINED", "Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "valueDensity": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "version": "4.0", "baseSeverity": "HIGH", "baseScore": 8.7, "vectorString": "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" } } ], "timeline": [ { "time": "2026-07-09T12:11:00.000Z", "lang": "en", "value": "reported to the Apache Security Team" }, { "time": "2026-07-10T12:11:00.000Z", "lang": "en", "value": "reported issues fixed on develop (a2dbb6bfc0, 5a4d5bdb4c)" }, { "time": "2026-09-07T12:12:00.000Z", "lang": "en", "value": "Apache PLC4X 1.0.0 released with the fixes" } ], "credits": [ { "lang": "en", "value": "Abhinav Agarwal", "type": "finder" } ], "x_generator": { "engine": "Vulnogram 1.0.3" } }, "adp": [ { "metrics": [ { "other": { "type": "ssvc", "content": { "timestamp": "2026-09-30T14:39:55.913450Z", "id": "CVE-2026-102509", "options": [ { "Exploitation": "none" }, { "Automatable": "yes" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "version": "2.0.3" } } } ], "title": "CISA ADP Vulnrichment", "providerMetadata": { "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-09-30T14:40:06.881Z" } } ] } }