# CVE-2026-1789: Information disclosure in MF842CDW

> An administrator can access sensitive device information via crafted requests in the browser-based remote management interface of Canon printers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-jh49-rh44-24pq

## What is CVE-2026-1789?

CVE-2026-1789 is a medium-severity vulnerability in Canon Inc. MF842CDW, published on 23 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the browser-based remote management interface may allow an administrator to access sensitive information on the device via crafted requests, affecting certain production printers and office/small office multifunction printers.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

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


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

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

## Is CVE-2026-1789 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1789 is a medium-severity vulnerability in Canon Inc. MF842CDW, published on 23 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1789 in the wild and no public exploit code.

Affected product: Canon Inc. MF842CDW. 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-1789/ (Markdown: https://insights.sbomify.com/CVE-2026-1789/index.md)
```

## Sources

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

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