Skip to content
Applications

CVE-2026-50100

8.5
High
EPSS 0.13%Jun 15, 2026

Privilege escalation via crafted driver in Ricoh/Konica printer drivers.

common questions

Is CVE-2026-50100 being exploited?

Not confirmed. CVE-2026-50100 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-50100?

CVE-2026-50100 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-50100?

Not known from our data. No patch reference has been recorded for CVE-2026-50100, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-50100 affect?

CVE-2026-50100 affects Ricoh printer drivers, KONICA MINOLTA printer drivers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-50100?

Update drivers when vendor releases a fix.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Ricoh printer driversKONICA MINOLTA printer drivers
impact

Local privilege escalation: login user can elevate privileges with a crafted driver.

action required

Patch when possible

affected versions
Ricoh Company, Ltd. Multiple printer drivers
  • affectedsee the information provided by the vendor
KONICA MINOLTA JAPAN, INC. Multiple printer drivers
  • affectedsee the information provided by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free