CVE-2026-102508

CRITICALPre-NVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd 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
9.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 9.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Verification of Cryptographic Signature and Improper Certificate Validation in the OPC UA driver of Apache PLC4X (PLC4J) allows an attacker in a network position between client and server to impersonate the OPC UA server and to read, forge or modify secure-channel traffic, including user credential ssent by the client.

The defect manifests differently depending on the version:

  • In 0.9.0 through 0.11.0 a failed message-signature check is only logged and never enforced, and there is no mechanism to verify the server certificate: it is taken from the unauthenticated GetEndpoints discovery response and used to encrypt the user's password.
  • In 0.12.0 through 0.13.1 the signature check is inverted (valid signatures are rejected, invalid ones accepted), and server certificates are accepted without a trust anchor by default.
  • In all affected versions the default security policy is None. Starting with 0.12.0 the driver additionally continues silently at a weaker security policy than the one configured, and starting with 0.13.0 endpoint selection prefers the weakest matching endpoint.

Users checking only for one of these mechanisms may wrongly conclude they are unaffected.

This issue affects Apache PLC4X: from 0.9.0 before 1.0.0.

Users are recommended to upgrade to version 1.0.0, which fixes the issue. Version 1.0.0 verifies message signatures correctly, refuses to connect unless the server certificate can be verified against a configured trust store or pinned certificate, defaults to Basic256Sha256 with SignAndEncrypt, and fails the connection if the negotiated security policy is weaker than the configured one.

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
41
EG Risk 41/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
Severity92% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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/o076mcnsx6wnqpdy780m7s6hddbbnjfw

Vendor Advisories for CVE-2026-102508(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 43× in last 7d / 43× 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-04 10:29 UTCGHSA enrichment
  2. 2026-10-04 06:45 UTCGHSA enrichment
  3. 2026-10-04 03:01 UTCGHSA enrichment
  4. 2026-10-03 23:17 UTCGHSA enrichment
  5. 2026-10-03 19:33 UTCGHSA enrichment
  6. 2026-10-03 15:50 UTCEG score recompute
  7. 2026-10-03 15:49 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 12:04 UTCGHSA enrichment
  10. 2026-10-03 08:19 UTCGHSA enrichment
  11. 2026-10-03 04:33 UTCGHSA enrichment
  12. 2026-10-03 00:49 UTCGHSA enrichment
  13. 2026-10-02 21:05 UTCGHSA enrichment
  14. 2026-10-02 17:19 UTCEG score recompute
  15. 2026-10-02 17:19 UTCGHSA enrichment
  16. 2026-10-02 13:34 UTCGHSA enrichment
  17. 2026-10-02 09:50 UTCGHSA enrichment
  18. 2026-10-02 06:07 UTCGHSA enrichment
  19. 2026-10-02 02:23 UTCGHSA enrichment
  20. 2026-10-01 22:37 UTCEG score recompute
  21. 2026-10-01 22:37 UTCGHSA enrichment
  22. 2026-10-01 19:49 UTCEPSS rescore
  23. 2026-10-01 18:52 UTCGHSA enrichment
  24. 2026-10-01 15:08 UTCGHSA enrichment
  25. 2026-10-01 11:24 UTCGHSA enrichment
Show 18 more
  1. 2026-10-01 07:41 UTCGHSA enrichment
  2. 2026-10-01 03:57 UTCGHSA enrichment
  3. 2026-10-01 00:14 UTCGHSA enrichment
  4. 2026-09-30 20:08 UTCGHSA enrichment
  5. 2026-09-30 16:24 UTCGHSA enrichment
  6. 2026-09-30 15:38 UTCEG score recompute
  7. 2026-09-30 15:38 UTCGHSA enrichment
  8. 2026-09-30 15:02 UTCEPSS rescore
  9. 2026-09-30 14:53 UTCEG score recompute
  10. 2026-09-30 14:53 UTCGHSA enrichment
  11. 2026-09-30 14:35 UTCGHSA enrichment
  12. 2026-09-30 10:33 UTCEG score recompute
  13. 2026-09-30 10:32 UTCGHSA enrichment
  14. 2026-09-30 10:15 UTCEG score recompute
  15. 2026-09-30 10:15 UTCGHSA enrichment
  16. 2026-09-30 08:18 UTCEG score recompute
  17. 2026-09-30 07:55 UTCEG score recompute
  18. 2026-09-30 07:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102508?
CVE-2026-102508 is a critical vulnerability published on September 30, 2026. Improper Verification of Cryptographic Signature and Improper Certificate Validation in the OPC UA driver of Apache PLC4X (PLC4J) allows an attacker in a network position between client and server to impersonate the OPC UA server and to read, forge or modify secure-channel traffic, including user…
When was CVE-2026-102508 disclosed?
CVE-2026-102508 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-102508 actively exploited?
CVE-2026-102508 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102508?
CVE-2026-102508 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102508?
A fix for CVE-2026-102508 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-102508 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-102508?

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

Book a Demo →Browse All CVEs