CVE-2026-102511: Improper Verification of Source of a Communication Channel in the ADS discovery of the Go implementation of Apache PLC4X (PLC4Go) allows an attacker
Source GCVE Database
Not known to be exploited · CVSS 8.5 High : upgrade to 1.0.0 soon.
Data as of 14 Nov 2026, 20:43 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.0
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Apache PLC4X and github.com/apache/plc4x/plc4go and Apache Software Foundation/org.apache.plc4x:plc4j-driver-ads and Apache Software Foundation/org.apache.plc4x:plc4j-driver-modbus and Apache Software Foundation/org.apache.plc4x:plc4j-driver-eip to 1.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache PLC4X | Affected
| Fixed in
|
| Apache Software FoundationApache PLC4X | Affected
| Fixed in
|
GitHubgithub.com/apache/plc4x/plc4gopkg:github/github.com/apache/plc4x/plc4goOther threats | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.plc4x:plc4j-driver-adspkg:maven/Apache Software Foundation/org.apache.plc4x:plc4j-driver-adsOther threats | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.plc4x:plc4j-driver-modbuspkg:maven/Apache Software Foundation/org.apache.plc4x:plc4j-driver-modbusOther threats | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.plc4x:plc4j-driver-eippkg:maven/Apache Software Foundation/org.apache.plc4x:plc4j-driver-eipOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to Apache PLC4X version 1.0.0 or later, which fixes the vulnerability by deriving connection addresses from the datagram's actual source address and logging warnings when discrepancies occur. This upgrade also addresses denial-of-service conditions caused by malformed datagrams. No other mitigation is required as the fix is official and available.
Description
A vulnerability in the ADS discovery mechanism of Apache PLC4X's Go implementation (PLC4Go) and Java implementation (PLC4J) allows an attacker who can send UDP datagrams to the discovering host to redirect connections to arbitrary addresses. The issue arises because the connection address is derived from the claimed AmsNetId in the response body rather than the actual source address of the datagram. This can lead to an attacker inserting malicious inventory entries and intercepting ADS sessions with route credentials. Additionally, malformed datagrams can disrupt discovery listeners, causing them to stop or consume excessive CPU resources. The vulnerability affects versions prior to 1.0.0 and is fixed in version 1.0.0, which correctly derives connection addresses from the datagram source and logs warnings on mismatches.