# CVE-2026-50100: Privilege escalation in Multiple printer drivers

> An attacker with local access can elevate privileges by exploiting a vulnerability in Ricoh and Konica Minolta printer drivers.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-7c4j-4vwf-c9vr

## What is CVE-2026-50100?

CVE-2026-50100 is a high-severity vulnerability in KONICA MINOLTA JAPAN, INC. Multiple printer drivers, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple printer drivers provided by Ricoh Company, Ltd. and KONICA MINOLTA JAPAN, INC. contain a privilege escalation vulnerability. If this vulnerability is exploited, an attacker who can log in to a computer running an affected printer driver could elevate privileges by using a specially crafted driver.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-50100 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50100 is a high-severity vulnerability in KONICA MINOLTA JAPAN, INC. Multiple printer drivers, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50100 in the wild and no public exploit code.

Affected product: KONICA MINOLTA JAPAN, INC. Multiple printer drivers. 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-50100/ (Markdown: https://insights.sbomify.com/CVE-2026-50100/index.md)
```

## Sources

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

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