CVE-2026-102510

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 https://cveprocess.apache.org/cve5/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. 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.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 30, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 30, 2026
Fix named in the CVE record.
generic

Pony Mail

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

Vendor Advisories for CVE-2026-102510(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 22:30 UTCEG score recompute
  2. 2026-10-03 22:29 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 09:28 UTCGHSA enrichment
  5. 2026-10-02 20:27 UTCEG score recompute
  6. 2026-10-02 20:26 UTCGHSA enrichment
  7. 2026-10-02 07:23 UTCEG score recompute
  8. 2026-10-02 07:23 UTCGHSA enrichment
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-10-01 18:24 UTCGHSA enrichment
  11. 2026-10-01 05:23 UTCGHSA enrichment
  12. 2026-09-30 16:23 UTCGHSA enrichment
  13. 2026-09-30 15:38 UTCEG score recompute
  14. 2026-09-30 15:38 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-30 14:53 UTCEG score recompute
  17. 2026-09-30 14:53 UTCGHSA enrichment
  18. 2026-09-30 09:28 UTCEG score recompute
  19. 2026-09-30 08:30 UTCEG score recompute
  20. 2026-09-30 08:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102510?
CVE-2026-102510 is a high vulnerability published on September 30, 2026. 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…
When was CVE-2026-102510 disclosed?
CVE-2026-102510 was first published on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102510 actively exploited?
CVE-2026-102510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102510?
CVE-2026-102510 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102510?
A fix for CVE-2026-102510 is available — its CVE record says: "Users are recommended to upgrade to version 1.0.0, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-102510 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-102510

Explore →

Is Your Infrastructure Affected by CVE-2026-102510?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs