CVE-2026-102510 and CVE-2026-102509: Integer Overflow, Improper Validation of Array Index, Uncontrolled Recursion and Memory Allocation with Excessive Size Value in the Go implementation of Apache PLC4X (PLC4Go) allow a malicious device, or an attacker able to inject network traffic, to crash or exhaust the memory of the client application, causing a denial of service
This Apache advisory covers CVE-2026-102510 and CVE-2026-102509 in Apache PLC4X. Its rating, versions and guidance apply to the bulletin as a whole, not to each of its 2 CVEs.
Key facts
- Bulletin rating
- High, CVSS 8.7
- Affected
- 0.11.0 before 1.0.0; through 0.13.1
- Fixed in
- 1.0.0
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
Integer Overflow, Improper Validation of Array Index, Uncontrolled Recursion and Memory Allocation with Excessive Size Value in the Go implementation of Apache PLC4X (PLC4Go) allow a malicious device, or an attacker able to inject network traffic, to crash or exhaust the memory of the client application, causing a denial of service.
The individual defects are:
- Generated parsers pre-allocate arrays with the element count claimed on the wire (0.13.0 through 0.13.1).
- Transport read helpers allocate buffers of the size claimed on the wire without an upper bound.
- ADS and KNXnet/IP response handling indexes into received data without checking its length, causing a panic.
- ADS and EIP frame-length handling accepts, or arithmetically wraps to, a length of zero, breaking message framing.
- Recursive protocol types are parsed without a nesting-depth limit. The same defect in the Java implementation is covered by CVE-2026-102509.
Additionally, length and position arithmetic in generated serializers was performed in 16-bit integers. If an application forwards attacker-influenced payloads larger than 8 KB, the length field wraps, and the remainder of the payload may be interpreted by the receiving device (for example, an ADS PLC) as
additional, independent protocol messages.
This issue affects Apache PLC4X: from 0.11.0 before 1.0.0.
Text from the source record.
- 0.11.0 before 1.0.0
- through 0.13.1
Official advisory · high-confidence parse· fetched ·verify at source
Fix and mitigation
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- The individual defects are: - Generated parsers pre-allocate arrays with the element count claimed on the wire (0.13.0 through 0.13.1). - Transport read helpers allocate buffers of the size claimed on the wire without an upper bound. - ADS and KNXnet/IP response handling indexes into received data without checking its length, causing a panic. - ADS and EIP frame-length handling accepts, or arithmetically wraps to, a length of zero, breaking message framing. - Recursive protocol types are parsed without a nesting-depth limit.
- Users are recommended to upgrade to version 1.0.0, which fixes the issue.
More Apache Software Foundation advisories
CVE-2026-102511Sep 30, 2026Improper Verification of Source of a Communication Channel in the ADS discovery of the GoCVE-2026-102509Sep 30, 2026Memory Allocation with Excessive Size Value, Allocation of Resources Without LimitsCVE-2026-102508Sep 30, 2026Improper Verification of Cryptographic Signature and Improper Certificate ValidationCVE-2026-96295Nov 20, 2026Apache Texera: Authenticated users can bypass normal controls on the reading and writingCVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-133325Nov 19, 2026Key exchange without entity authentication vulnerability in Apache Tomcat
Apache Software Foundation advisories, September 2026All Apache Software Foundation advisories
Get an email when Apache publishes the next one.
See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.