# CVE-2026-21409: Information disclosure in RICOH Streamline NX

> A man-in-the-middle attack allows retrieval of user registration information and OIDC tokens from RICOH Streamline NX.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-842v-gv8w-xp7c

## What is CVE-2026-21409?

CVE-2026-21409 is a high-severity vulnerability in RICOH Streamline NX, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper authorization vulnerability exists in RICOH Streamline NX 3.5.1 to 24R3. If a man-in-the-middle attack is conducted on the communication between the affected product and its user, and some crafted request is processed by the product, the user's registration information and/or OIDC (OpenID Connect) tokens may be retrieved.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-21409?


## How do I fix CVE-2026-21409?

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

## Is CVE-2026-21409 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21409 and fix it if it is affected.

What it is: CVE-2026-21409 is a high-severity vulnerability in RICOH Streamline NX, published on 9 Jan 2026. 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-2026-21409 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-2026-21409/ (Markdown: https://insights.sbomify.com/CVE-2026-21409/index.md)
```

## Sources

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

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