dbcve.org
Mf455dw FirmwareOperating system · Canon

CVE-2025-14232

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to after 06.02 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer overflow in XML processing of XPS file in Small Office Multifunction Printers and Laser Printers(*) which may allow an attacker on the network segment to trigger the affected product being unresponsive or to execute arbitrary code. *: Satera LBP670C Series/Satera MF750C Series firmware v06.02 and earlier sold in Japan.Color imageCLASS LBP630C/Color imageCLASS MF650C Series/imageCLASS LBP230 Series/imageCLASS X LBP1238 II/imageCLASS MF450 Series/imageCLASS X MF1238 II/imageCLASS X MF1643i II/imageCLASS X MF1643iF II firmware v06.02 and earlier sold in US.i-SENSYS LBP630C Series/i-SENSYS MF650C Series/i-SENSYS LBP230 Series/1238P II/1238Pr II/i-SENSYS MF450 Series/i-SENSYS MF550 Series/1238i II/1238iF II/imageRUNNER 1643i II/imageRUNNER 1643iF II firmware v06.02 and earlier sold in Europe.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in the XML processing component when handling XPS (XML Paper Specification) files on Canon Satera and i-SENSYS multifunction printers and laser printers. The vulnerability allows a network-adjacent attacker to potentially crash the device or execute arbitrary code by sending specially crafted XPS files, due to insufficient bounds checking during XML parsing.

MitigationUpdate printer firmware to version v06.03 or later as released by Canon, and restrict network access to trusted devices only to reduce the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mf455dw FirmwareOperating system
Affected:<= 06.02
Mf453dw FirmwareOperating system
Affected:<= 06.02
Mf452dw FirmwareOperating system
Affected:<= 06.02
Mf451dw FirmwareOperating system
Affected:<= 06.02
Mf654cdw FirmwareOperating system
Affected:<= 06.02
Mf656cdw FirmwareOperating system
Affected:<= 06.02
Mf653cdw FirmwareOperating system
Affected:<= 06.02
Mf652cw FirmwareOperating system
Affected:<= 06.02

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the printer model
    Access the printer's web administration panel, check the device status page, or query the device via SNMP (OID 1.3.6.1.2.1.1.1 for sysDescr) to confirm the exact model number
    Affected if The model is one of: MF455dw, MF453dw, MF452dw, MF451dw, MF654cdw, MF656cdw, MF653cdw, or MF652cw
  2. Check the installed firmware version
    In the printer web interface, navigate to the Firmware Update or Device Information section. Alternatively, print a configuration page or use SNMP (OID 1.3.6.1.2.1.47.1.1.1 for entity-mib) to retrieve the firmware version
    Affected if The firmware version is 06.02 or lower (e.g., 06.02, 06.01, 05.x, etc.)
  3. Verify if XPS print job submission is accessible
    Check the printer's network services configuration: confirm if IPP (port 631) or raw print ports (9100) are open and accessible on the network. In the web interface, review the allowed print protocols under Network Settings or Print Service settings
    Affected if The printer accepts XPS print jobs via IPP or direct print port and is accessible from the network segment where an attacker resides
  4. Confirm XML processing is enabled for XPS files
    In the printer web interface, examine the Print Feature settings or Job Processing settings. Look for options related to XPS support, XML parsing, or direct document printing. If using a print server, check if XPS spooling is enabled
    Affected if XPS or XML-based print job processing is enabled and the printer will parse XML content from submitted print files

The device is vulnerable if it is one of the listed Canon models (MF455dw, MF453dw, MF452dw, MF451dw, MF654cdw, MF656cdw, MF653cdw, or MF652cw) running firmware version 06.02 or lower and XPS/XML print job submission is accessible from the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 06.02
Interim mitigation

Update printer firmware to version v06.03 or later as released by Canon, and restrict network access to trusted devices only to reduce the attack surface.

Recommended fix Moderate confidence

Canon firmware version 06.03 or later (specific to your model)

  1. 1. Identify the exact Canon printer model from the affected product list (Mf455dw, Mf453dw, Mf452dw, Mf451dw, Mf654cdw, Mf656cdw, Mf653cdw, Mf652cw or regional equivalents)
  2. 2. Access the printer's web interface or control panel to check the current firmware version
  3. 3. Navigate to Canon's official support page for your specific printer model (from canon.jp, www.usa.canon.com, or www.canon-europe.com depending on region)
  4. 4. Download the latest firmware version available - look for version 06.03 or later
  5. 5. Follow Canon's firmware update instructions provided on the support page, typically involving uploading the firmware file through the printer's web interface or USB connection
  6. 6. After update, verify the firmware version has changed from <=06.02 to the newer version
Caveat Firmware updates typically do not introduce breaking changes but may reset some network settings; backup configuration if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mf455dw Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14232 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data