TI-2026-65417 Aliases CVE-2026-102511 GHSA-jfxw-f7pw-76rc

Improper array index validation in Apache PLC4X

LOW 38CWE-129Published 2026-09-30 · Updated 2026-09-30

Key facts

Attack vector: Adjacent network
Privileges required: None
User interaction: Passive
Attack complexity: Low
Attack requirements: None
Impact type: Code execution, Denial of service
Confidentiality · integrity · availability: High · High · None
Fix status: Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-129, CWE-248 and the CVSS impact.

Summary

Improper Verification of Source of a Communication Channel in the ADS discovery of the Go implementation of Apache PLC4X (PLC4Go) allows an attacker able to send UDP datagrams to the discovering host to redirect subsequent connections to an arbitrary, attacker-chosen address. The discovery result's connection address was derived from the AmsNetId claimed in the response body rather than from the datagram's actual source address. One spoofed discovery response can therefore insert an inventory entry pointing at any host, including hosts outside the local network, and an application that connects to discovered devices will open its ADS session, including any configured route credentials, to that host. Additionally, discovery listeners in both implementations can be disabled by a single malformed datagram: - In PLC4Go ADS discovery, a short version block causes a panic that ends the listener for the rest of the discovery call, so legitimate devices answering afterwards are not reported. - In PLC4J, the ADS and EtherNet/IP discoverers stop on an unhandled exception from a malformed response. - The PLC4J Modbus discoverer can be made to spin indefinitely, consuming a CPU core, by a scanned host that sends a partial response. Exploitation requires the application to invoke the discovery API, which is opt-in, and for the connection redirect, to act on the discovered items. This issue affects Apache PLC4X: PLC4Go from 0.11.0 before 1.0.0; PLC4J ADS and Modbus drivers from 0.10.0 before 1.0.0; PLC4J EtherNet/IP driver from 0.11.0 before 1.0.0. PLC4Go is consumed as the Go module github.com/apache/plc4x/plc4go; versions refer to the corresponding Apache PLC4X releases. Users are recommended to upgrade to version 1.0.0, which fixes the issue. Version 1.0.0 derives the connection address from the datagram's source address and logs a warning when the claimed AmsNetId disagrees with it.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV

EPSS 0.00182 7th percentileScored 2026-11-07

Fix Fixed Apache PLC4X (Apache Software Foundation): 1.0.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation: None
Automatable: No
Technical impact: Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
Apache	Apache PLC4X	0.11.0 to before 1.0.0	1.0.0	Patch available	CNA
Apache	Apache PLC4X	0.10.0 to before 1.0.0	1.0.0	Patch available	CNA
Apache	Apache PLC4X	0.10.0 to before 1.0.0	1.0.0	Patch available	CNA
Apache	Apache PLC4X	0.11.0 to before 1.0.0	1.0.0	Patch available	CNA

Apache PLC4X VendorApache Affected 0.11.0 to before 1.0.0 Fixed in 1.0.0 Patch available CNA
Apache PLC4X VendorApache Affected 0.10.0 to before 1.0.0 Fixed in 1.0.0 Patch available CNA
Apache PLC4X VendorApache Affected 0.10.0 to before 1.0.0 Fixed in 1.0.0 Patch available CNA
Apache PLC4X VendorApache Affected 0.11.0 to before 1.0.0 Fixed in 1.0.0 Patch available CNA

Remediation

Fix · CNA Apache PLC4X (Apache Software Foundation) Fixed in 1.0.0
Fix · CNA Apache PLC4X (Apache Software Foundation) Fixed in 1.0.0
Fix · CNA Apache PLC4X (Apache Software Foundation) Fixed in 1.0.0
Fix · CNA Apache PLC4X (Apache Software Foundation) Fixed in 1.0.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

Release · 2026-09-30
Apache PLC4X 1.0.0
4 records Highest priority Priority MEDIUM 3 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2026-65416 Apache PLC4X: Go binding: unbounded allocation and framing failures on wire-controlled lengthsPriority MEDIUM 44
- TI-2026-65415 Apache PLC4X, Apache PLC4X: Pre-authentication resource exhaustion in the OPC UA driver and the Java SPI parserPriority MEDIUM 44
- TI-2026-65414 Apache PLC4X: OPC UA secure channel: integrity bypass, unverifiable server certificate, and silent downgradePriority MEDIUM 41
Show all 4 records →

Timeline

2026-10-02 Threatist record created from CVE-2026-102511
2026-10-03 Alias added: GHSA-jfxw-f7pw-76rc

References

Advisory 1

https://lists.apache.org/thread.html/g692j4fklrbo80stjr5ll8xghrwszthf

TI-2025-18529 Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUT KEVCVSS 3.1CRITICAL 10.0
TI-2024-30292 Apache OFBiz: Confused controller-view authorization logic (forced browsing) KEVCVSS 3.1CRITICAL 9.8
TI-2024-26062 Apache OFBiz: Unauthenticated endpoint could allow execution of screen rendering code KEVCVSS 3.1CRITICAL 9.8
TI-2024-21190 Apache OFBiz: Path traversal leading to RCE KEVCVSS 3.1CRITICAL 9.8
TI-2024-18186 Apache HugeGraph-Server: Command execution in gremlin KEVCVSS 3.1CRITICAL 9.8
TI-2023-25106 Deserialization of untrusted data in Apache ActiveMQ KEVCVSS 3.1CRITICAL 10.0

See all 4053 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences