VulnerabilityPublished 8 Sep 2025

CVE-2025-58422: RICOH Streamline NX · Use of Less Trusted Source

Affects RICOH Streamline NXSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.0 base score

3.1Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 8 Sep 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Ensure all communications with RICOH Streamline NX management tools are conducted over secure, encrypted channels such as HTTPS with strong TLS configurations to prevent MitM attacks. 2) Employ network segmentation and strict firewall rules to limit access to the management interface only to trusted administrative hosts and networks. 3) Use VPNs or other secure remote access solutions when remote management is necessary to reduce exposure to interception. 4) Monitor network traffic for unusual patterns that may indicate MitM attempts or unauthorized access. 5) Regularly review and verify operation history logs for inconsistencies or signs of tampering. 6) Engage with Ricoh support channels to obtain patches or updates as they become available and apply them promptly. 7) Educate users and administrators about the risk of interacting with suspicious links or prompts that could facilitate user interaction required for exploitation. These targeted actions go beyond generic advice by focusing on securing communication channels and monitoring integrity of audit logs specific to this vulnerability.

Description

RICOH Streamline NX versions 3.5.1 to 24R3 are vulnerable to tampering with operation history. If an attacker can perform a man-in-the-middle attack, they may alter the values of HTTP requests, which could result in tampering with the operation history of the product’s management tool.

Impact

For European organizations using RICOH Streamline NX, this vulnerability poses a risk primarily to the integrity of operational audit logs. Since the operation history can be tampered with, attackers could potentially cover their tracks after unauthorized access or malicious activities, complicating incident response and forensic investigations. This undermines trust in the system's audit capabilities, which are often critical for compliance with European regulations such as GDPR and NIS Directive that mandate reliable logging and monitoring. However, the low CVSS score and the requirement for a man-in-the-middle attack with user interaction reduce the likelihood of widespread exploitation. The impact is less severe on confidentiality and availability, but the integrity compromise could still facilitate insider threats or targeted attacks aiming to evade detection. Organizations relying heavily on RICOH Streamline NX for document workflow and management should be aware of this risk, especially in environments where sensitive or regulated data is processed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Sep 2025, 04:46 UTC

Technical details

References

Community reviews

Related threats