Answer in brief
CVE-2026-102511 records a High severity (CVSS 8.5) vulnerability in Apache PLC4X, Apache PLC4X, Apache PLC4X, Apache PLC4X: ADS discovery accepts spoofed responses and derives the connection target from them. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/github.com/apache/plc4x/plc4go (generic), Apache Software Foundation/org.apache.plc4x:plc4j-driver-ads (generic), Apache Software Foundation/org.apache.plc4x:plc4j-driver-eip (generic), Apache Software Foundation/org.apache.plc4x:plc4j-driver-modbus (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/github.com/apache/plc4x/plc4go (generic), Apache Software Foundation/org.apache.plc4x:plc4j-driver-ads (generic), Apache Software Foundation/org.apache.plc4x:plc4j-driver-eip (generic), Apache Software Foundation/org.apache.plc4x:plc4j-driver-modbus (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/github.com/apache/plc4x/plc4gogeneric | >=0.11.0 <1.0.0 | 1.0.0 |
| Apache Software Foundation/org.apache.plc4x:plc4j-driver-adsgeneric | >=0.10.0 <1.0.0 | 1.0.0 |
| Apache Software Foundation/org.apache.plc4x:plc4j-driver-eipgeneric | >=0.11.0 <1.0.0 | 1.0.0 |
| Apache Software Foundation/org.apache.plc4x:plc4j-driver-modbusgeneric | >=0.10.0 <1.0.0 | 1.0.0 |
Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.