# CVE-2025-46783: Path traversal in RICOH Streamline NX V3 PC Client

> Attackers can execute arbitrary code on user PCs by exploiting a path traversal flaw in the RICOH Streamline NX V3 PC Client.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2025
- **Updated:** 13 Jun 2025
- **Also known as:** GHSA-925q-2ff6-6j9x

## What is CVE-2025-46783?

CVE-2025-46783 is a critical path traversal vulnerability in RICOH Streamline NX V3 PC Client, published on 13 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Path traversal vulnerability exists in RICOH Streamline NX V3 PC Client versions 3.5.0 to 3.242.0. If this vulnerability is exploited, arbitrary code may be executed on the PC where the product is running by tampering with specific files used on the product.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-46783 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46783 is a critical path traversal vulnerability in RICOH Streamline NX V3 PC Client, published on 13 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46783 in the wild and no public exploit code.

Affected product: RICOH Streamline NX V3 PC Client. 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-46783/ (Markdown: https://insights.sbomify.com/CVE-2025-46783/index.md)
```

## Sources

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

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