Description
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.
Published: 2026-09-30
Score: 9.2 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized access and tampering with OPC UA secure channel traffic, including credentials
Action: Immediate Patch
AI Analysis

Impact

Apache PLC4X’s OPC UA driver fails to enforce or incorrectly verifies cryptographic signatures and server certificates. An attacker positioned between client and server can impersonate the OPC UA server, read, forge, or alter secure‑channel traffic, including credentials sent by the client. The flaw spans multiple versions and exposes clients to man‑in‑the‑middle attacks and data tampering.

Affected Systems

Apache Software Foundation’s PLC4X package versions 0.9.0 through 0.11.0, 0.12.0 through 0.13.1, and any release prior to 1.0.0 are vulnerable. All affected distributions use the default security policy ‘None’, and the driver may silently downgrade to a weaker policy or accept unverified certificates.

Risk and Exploitability

The vulnerability has a CVSS score of 9.2 and is not listed in the CISA KEV catalog. Because the EPSS score is not available, a precise exploitation likelihood cannot be quantified but the flaw permits a network attacker between the PLC client and server to intercept and modify traffic. The attack vector is inferred to be remote, exploiting the lack of signature enforcement and certificate validation during the secure‑channel establishment.

Generated by OpenCVE AI on September 30, 2026 at 11:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Apache PLC4X 1.0.0 or later, which correctly verifies message signatures and requires certificate validation against a trust store or pinned certificate.
  • Configure the driver to use a strong security policy such as Basic256Sha256 with SignAndEncrypt, and ensure that any negotiated policy is not weaker than the configured one.
  • Disable or restrict use of the default ‘None’ security policy and block endpoints that allow insecure or downgraded connections.

Generated by OpenCVE AI on September 30, 2026 at 11:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 30 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 30 Sep 2026 10:30:00 +0000

Type Values Removed Values Added
References

Wed, 30 Sep 2026 09:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache plc4x
Vendors & Products Apache
Apache plc4x

Wed, 30 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache PLC4X: OPC UA secure channel: integrity bypass, unverifiable server certificate, and silent downgrade
Weaknesses CWE-295
CWE-347
CWE-757
References
Metrics cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-09-30T14:39:33.687Z

Reserved: 2026-09-29T11:40:54.414Z

Link: CVE-2026-102508

cve-icon Vulnrichment

Updated: 2026-09-30T10:08:10.861Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-30T08:16:31.903

Modified: 2026-09-30T16:14:10.347

Link: CVE-2026-102508

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-30T11:30:18Z

Weaknesses
  • CWE-295

    Improper Certificate Validation

  • CWE-347

    Improper Verification of Cryptographic Signature

  • CWE-757

    Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')