CVE-2025-46358VulnerabilityPublished 10 Jul 2025

CVE-2025-46358: Emerson ValveLink SOLO · CWE-693

Affects Emerson ValveLink SOLOSource CVE Database V5

Not known to be exploited · CVSS 7.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.7High

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

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

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

Attack Vector: Local
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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 10 Jul 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 wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Emerson ValveLink SOLO	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-46358, European organizations should implement a multi-layered security approach tailored to industrial control environments. First, strictly enforce network segmentation and access controls to limit local access to ValveLink SOLO systems only to authorized personnel and trusted devices. Use network monitoring and anomaly detection tools specialized for ICS to identify unusual access patterns or configuration changes. Since no patches are currently available, organizations should engage with Emerson for updates and apply patches promptly once released. Employ host-based security controls on systems running ValveLink SOLO, such as application whitelisting and integrity monitoring, to detect unauthorized modifications. Conduct regular security audits and vulnerability assessments focused on ICS components. Additionally, implement strong physical security controls to prevent unauthorized physical access to devices. Train staff on insider threat awareness and secure operational procedures. Finally, consider deploying compensating controls such as multi-factor authentication for accessing ValveLink SOLO interfaces if supported, and maintain up-to-date incident response plans specific to ICS environments.

Description

Emerson ValveLink products do not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Impact

For European organizations, the impact of CVE-2025-46358 could be substantial, particularly for those operating critical infrastructure and industrial environments where Emerson ValveLink SOLO is deployed. The high confidentiality and integrity impact means that attackers could potentially access sensitive operational data or alter valve configurations, leading to incorrect valve operations. This could disrupt industrial processes, cause safety hazards, or lead to production downtime. Although availability is not directly impacted, the indirect consequences of compromised integrity and confidentiality could result in operational interruptions or safety incidents. European industries such as energy production, water treatment, and manufacturing that rely on precise valve control are at risk. Additionally, regulatory frameworks like NIS2 and GDPR emphasize the protection of critical infrastructure and personal data, so exploitation of this vulnerability could lead to compliance violations and financial penalties. The requirement for local access somewhat limits the attack surface to insiders or attackers who have gained foothold within the network, but the lack of required privileges or user interaction lowers the barrier once local access is achieved. This elevates the risk of insider threats or lateral movement by attackers within industrial networks.

CWE-693Protection Mechanism Failure (opens in a new tab)
Pillar weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Site Tracing (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Encryption Brute Forcing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 14:16 UTC

WeaknessesCWE-693

Technical details

References

Community reviews

Related threats