CVE-2025-52579VulnerabilityPublished 10 Jul 2025

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

Affects Emerson ValveLink SOLOSource CVE Database V5

Not known to be exploited · CVSS 9.4 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.4Critical

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% 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:L

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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

Mitigation should focus on immediate and practical steps beyond generic advice. First, organizations should implement strict network segmentation and access controls to limit exposure of ValveLink SOLO systems to trusted personnel and networks only. Monitoring and logging of access to these systems should be enhanced to detect anomalous activities. Employing memory protection techniques such as encrypted memory or secure coding practices in custom integrations can reduce risk. Regularly capturing and securely handling core dumps and memory snapshots is critical; organizations should ensure these are encrypted and access-controlled. Incident response plans should be updated to include scenarios involving memory data leakage. Finally, organizations should maintain close communication with Emerson for forthcoming patches or mitigations and plan for timely deployment once available.

Description

Emerson ValveLink Products store sensitive information in cleartext in memory. The sensitive memory might be saved to disk, stored in a core dump, or remain uncleared if the product crashes, or if the programmer does not properly clear the memory before freeing it.

Impact

For European organizations, especially those in critical infrastructure sectors such as oil and gas, chemical manufacturing, water treatment, and power generation, the impact of this vulnerability could be severe. Emerson ValveLink SOLO is commonly deployed in process industries across Europe, and the exposure of sensitive information could lead to unauthorized access to control systems, manipulation of industrial processes, and potential safety hazards. Confidentiality breaches could expose proprietary process data or credentials, enabling further lateral movement within OT networks. Integrity compromises could allow attackers to alter control parameters, potentially causing physical damage or operational disruptions. Although availability impact is rated low, the cascading effects of compromised control systems could indirectly affect availability of services. The lack of authentication and user interaction requirements means that attackers with network access to the affected systems can exploit this vulnerability remotely, increasing the risk profile for European organizations that have ValveLink SOLO deployed in network-accessible environments without adequate segmentation or monitoring.

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, 00:01 UTC

WeaknessesCWE-316

Technical details

References

Community reviews

Related threats