OT/ICSCritical 9.2Patch available
CVE-2026-102508
OPC UA driver in Apache PLC4X allows MitM to read/modify secure-channel traffic and credentials
How scary is it?
updated 13 Oct 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Apache Software Foundation Apache PLC4X in an affected version>= 0.9.0 and < 1.0.0
Vendor says fixed in: 1.0.0.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Specific conditions are met that the attacker does not control
CVSS attack requirements: Present (AT:P). The attack depends on deployment or execution conditions. The CVE record does not always say which.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per the vendorUpgrade to a fixed release1.0.0
Fixed releases as stated by the vendor in the CVE record.
See the affected products table · Source 1
Recommendation, AI-writtenUpgrade to Apache PLC4X 1.0.0 and verify truststore/security policy settings
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. Affects Apache PLC4X OPC UA driver used in industrial connectivity; enables MitM of control traffic and credential theft — high-impact for OT environments and enterprise ICS deployments.
- CVSS
- 9.2Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.16%chance of exploitation in the next 30 daystop 96% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Fixed in 1.0.0per the vendor
- Published
- 30 Sept 2026analysed here 30 Sept 2026
Do first. Upgrade to a fixed release: 1.0.0.
Summary
Impact
Network MitM can impersonate OPC UA server to read, forge, or modify secure-channel traffic including user credentials; may enable command manipulation of OT systems.
Triage
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- No. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Apache Software Foundation Apache PLC4X | >= 0.9.0 and < 1.0.0Vendor says fixed in: 1.0.0 |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Apache PLC4X OPC UA driver versions 0.9.0 to before 1.0.0 (0.9.0-0.13.1)
- Any application or ICS/SCADA component using PLC4X for OPC UA communications
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. The vulnerability involves man-in-the-middle attacks on OPC UA protocol traffic, which is not HTTP-based, so a web application firewall cannot filter or block the malicious input.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 30 Sept 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 30 Sept 2026Published
- 30 Sept 2026Analysed by vulneraibility.comsame day later
- 30 Sept 2026CISA SSVC assessment: exploitation nonesame day later
- 30 Sept 2026CVE record last updatedsame day later
Common questions
Is CVE-2026-102508 being exploited?
Not confirmed. CVE-2026-102508 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-102508?
CVE-2026-102508 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102508?
Yes. A fix has been recorded for CVE-2026-102508. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102508 affect?
CVE-2026-102508 affects Apache PLC4X OPC UA driver versions 0.9.0 to before 1.0.0 (0.9.0-0.13.1), Any application or ICS/SCADA component using PLC4X for OPC UA communications. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102508?
Upgrade to Apache PLC4X 1.0.0 and verify truststore/security policy settings
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- lists.apache.org /thread.html/o076mcnsx6wnqpdy780m7s6hddbbnjfw
Other links (1)
- openwall.com /lists/oss-security/2026/09/30/4
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.