# CVE-2026-102510: Apache PLC4X PLC4Go denial of service via integer overflow and memory exhaustion

Source: https://junglewise.ai/threats/cve-2026-102510-integer-overflow-improper-validation-of-array-index-uncontrolled  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-30. Updated: 2026-09-30  
License: CC BY 4.0 with a link back

CVE-2026-102510 · Severity: info · Published 2026-09-30

Apache PLC4X's Go implementation (PLC4Go) contains multiple defects in parsing and validating network protocol messages that allow an attacker or compromised device to crash client applications or exhaust their memory. An attacker on the network can inject malicious protocol frames to trigger denial of service, affecting industrial control systems and applications that rely on PLC4X for device communication.

Technologies: [Apache PLC4X](https://junglewise.ai/threats/technologies/plc4x). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-102510 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102510 being exploited in the wild.

**How severe is CVE-2026-102510?** Informational severity, published 30 September 2026.

**Which products and versions are affected?** Apache PLC4X 0.11.0 through 0.13.1.

**Is there a fix for CVE-2026-102510?** A patch was published on 2026-09-30: Fixed in version 1.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-102510 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-102510?** Check whether you run Apache PLC4X at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability encompasses multiple weaknesses: unvalidated array pre-allocation based on wire-claimed sizes, unbounded buffer allocation in transport helpers, missing bounds checking in ADS/KNXnet/IP indexing operations, arithmetic wrapping in frame-length handling, and uncontrolled recursion depth in protocol parsing. Additionally, 16-bit arithmetic in serializers causes length field wrapping for payloads over 8 KB, allowing remainder interpretation as independent protocol messages. An attacker with network access can exploit these via malformed protocol messages to cause memory exhaustion or application crashes.

## Affected products

- Apache PLC4X 0.11.0 through 0.13.1

## Timeline

- 2026-09-30: disclosed
- 2026-09-30: patched: Fixed in version 1.0.0

## Related threats

- [Apache PLC4X denial of service in OPC UA driver](https://junglewise.ai/threats/cve-2026-102509-memory-allocation-with-excessive-size-value-allocation-of)
- [Apache PLC4X OPC UA driver cryptographic signature verification bypass](https://junglewise.ai/threats/cve-2026-102508-improper-verification-of-cryptographic-signature-and-improper)