CVE-2025-50109VulnerabilityPublished 10 Jul 2025

CVE-2025-50109: Emerson ValveLink SOLO · CWE-316

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 3% 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

1. Restrict local access to systems running Emerson ValveLink SOLO by enforcing strict physical and network access controls, including network segmentation and access control lists (ACLs) to limit exposure to trusted personnel only. 2. Implement host-based monitoring and intrusion detection systems to detect unauthorized access attempts or anomalous activities on devices hosting ValveLink SOLO. 3. Encrypt sensitive data at rest and in transit where possible, including applying disk encryption or secure storage solutions on devices to reduce the risk of cleartext data exposure. 4. Regularly audit and review access permissions and logs to identify potential unauthorized access or attempts to read sensitive resources. 5. Coordinate with Emerson for timely updates or patches, and subscribe to ICS-CERT or vendor advisories for vulnerability disclosures. 6. Employ network segmentation to isolate ICS networks from corporate IT networks and external internet access, minimizing the attack surface. 7. Conduct employee training focused on ICS security best practices and the importance of safeguarding physical and logical access to control systems. 8. Consider deploying application whitelisting and endpoint protection solutions tailored for ICS environments to prevent unauthorized software execution.

Description

Emerson ValveLink Products store sensitive information in cleartext within a resource that might be accessible to another control sphere.

Impact

For European organizations, particularly those operating in critical infrastructure sectors such as oil and gas, chemical processing, and manufacturing, this vulnerability poses a significant risk. Emerson ValveLink SOLO is commonly used in industrial control systems (ICS) to monitor and manage valve operations, which are critical for process safety and operational continuity. Exposure of sensitive information in cleartext could allow attackers to gain insights into system configurations or credentials, enabling unauthorized manipulation or disruption of valve controls. This could lead to process inefficiencies, safety incidents, or operational downtime. Given the interconnected nature of ICS environments, exploitation could facilitate lateral movement to other control systems, increasing the attack surface. European organizations with ICS environments that incorporate Emerson products may face regulatory scrutiny under frameworks like NIS2 or GDPR if sensitive operational data is compromised. The lack of a patch increases the urgency for implementing compensating controls to mitigate risk until a fix is available.

CWE-316Cleartext Storage of Sensitive Information in Memory (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext in memory.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (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-316

Technical details

References

Community reviews

Related threats