# CVE-2025-58422: Other in RICOH Streamline NX

> An attacker performing a man-in-the-middle attack can tamper with operation history in RICOH Streamline NX by altering HTTP requests.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-r277-f4fh-cwv4

## What is CVE-2025-58422?

CVE-2025-58422 is a low-severity vulnerability in RICOH Streamline NX, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-348 (Use of Less Trusted Source)

## Which versions are affected by CVE-2025-58422?


## How do I fix CVE-2025-58422?

No fix has been published for CVE-2025-58422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-58422 being exploited?

There is no known exploitation of CVE-2025-58422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58422 and fix it if it is affected.

What it is: CVE-2025-58422 is a low-severity vulnerability in RICOH Streamline NX, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-58422 in the wild and no public exploit code.

Affected product: RICOH Streamline NX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58422/ (Markdown: https://insights.sbomify.com/CVE-2025-58422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58422
- OSV: https://osv.dev/vulnerability/CVE-2025-58422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58422/
Summaries are generated and may contain mistakes; the official description above is the record.