CVE-2025-7390VulnerabilityPublished 08/21/2025Updated 03/27/2026

CVE-2025-7390: Softing OPC UA C++ SDK · Improper Certificate Validation

Affects Softing OPC UA C++ SDKSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 10/25/2026, 16:58:54 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wild: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Softing OPC UA C++ SDK	Affected =6.40	Fixed in–

AI-suggested

1. Monitor Softing's official channels closely for the release of security patches addressing CVE-2025-7390 and apply them immediately upon availability. 2. Until patches are available, implement strict network segmentation to isolate OPC UA servers from untrusted networks and clients, limiting exposure. 3. Employ additional certificate validation mechanisms at the network or application layer, such as mutual TLS with external validation or hardware security modules (HSMs) to enforce certificate trust. 4. Conduct thorough audits of OPC UA server configurations to ensure endpoints are correctly set to require and validate client certificates. 5. Use intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous OPC UA traffic patterns indicative of unauthorized access attempts. 6. Enforce strict access controls and logging on OPC UA servers to monitor and respond to suspicious client connections. 7. Educate operational technology (OT) and security teams about this vulnerability and the importance of certificate validation in OPC UA communications. 8. Consider deploying compensating controls such as VPNs or secure gateways that add an additional layer of authentication and encryption.

Description

A malicious client can bypass the client certificate trust check of an opc.https server when the server endpoint is configured to allow only secure communication.

Impact

The impact of CVE-2025-7390 is substantial for organizations relying on Softing's OPC UA C++ SDK for secure communications in industrial automation, manufacturing, energy, and critical infrastructure sectors. Successful exploitation allows attackers to bypass client certificate authentication, leading to unauthorized access to sensitive operational data and control systems. This can result in data confidentiality breaches, unauthorized command execution, and potential manipulation or disruption of industrial processes. Given the criticality of OPC UA in supervisory control and data acquisition (SCADA) systems and other industrial control systems (ICS), this vulnerability could facilitate espionage, sabotage, or operational downtime. The lack of required privileges and user interaction lowers the barrier for exploitation, increasing risk. Organizations worldwide using affected versions may face increased risk of targeted attacks, especially those in sectors where OPC UA is prevalent. The absence of known exploits currently provides a window for proactive mitigation, but the critical CVSS score underscores the urgency of addressing this vulnerability.

Weaknesses

CWE-295Improper Certificate Validation (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not validate, or incorrectly validates, a certificate.
Architecture and Design · Implementation
Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V9.2.1 (opens in a new tab)
V1.9.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…