Authentication bypass via skipped client certificate trust check
Published Aug 21, 2025 · Updated Mar 27, 2026
Improper certificate validation in Softing OPC UA products allows remote attackers to bypass client authentication over HTTPS. The opc.https server fails to enforce its client certificate trust check, but Softing has not published the responsible function or exact validation error. Exploitation requires a secure-only endpoint and grants unauthorized access with confidentiality and integrity impact, without a reported service interruption.
Summary
What happened
Improper certificate validation in Softing OPC UA products allows remote attackers to bypass client authentication over HTTPS. The opc.https server fails to enforce its client certificate trust check, but Softing has not published the responsible function or exact validation error. Exploitation requires a secure-only endpoint and grants unauthorized access with confidentiality and integrity impact, without a reported service interruption.
The record
- CVE
- CVE-2025-7390
- Published
- Aug 21, 2025
- Updated
- Mar 27, 2026
- Vendor
- Softing Industrial Automation GmbH
- Product
- OPC UA C++ SDK
- Classifications
- CWE-295, CAPEC-115, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.40 <=6.80
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo