CVE-2025-14235
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 · uneditedBuffer overflow in XPS font fpgm data processing on 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 confidenceBuffer overflow vulnerability in the XPS font fpgm (font program) table processing within Canon printer firmware versions v06.02 and earlier. An attacker on the same network segment can send a specially crafted XPS document containing malformed font fpgm data to trigger a buffer overflow, potentially causing denial of service or arbitrary code execution with the privileges of the embedded firmware.
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<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02<= 06.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Canon printer modelLocate the model name on the printer front panel, label, or packaging. Verify it matches one of the affected models: Mf656cdw, Mf653cdw, Mf652cw, Mf1238 Ii, Mf1643if Ii, Mf1643i Ii, Lbp237dw, or Lbp236dw.Affected if The printer model is NOT one of these eight listed models (in which case the CVE does not apply).
-
Check installed firmware versionAccess the printer web interface by entering its IP address in a browser. Navigate to the Settings, Device Information, or Firmware section. Locate the firmware version field and compare it to v06.02. If the version shows v06.02 or lower (for example v05.10, v06.00), the printer is in the affected range.Affected if The firmware version displays 06.02 or any version lower than 06.02.
-
Verify XPS or PostScript processing is enabledIn the printer web interface, locate the PDL (Page Description Language) settings, Print Settings, or Language settings menu. Check whether XPS printing, PostScript printing, or the XPS/PostScript processing capability is turned ON or enabled. If this option is disabled or unavailable, the vulnerable code path may not be reachable.Affected if XPS or PostScript processing is enabled in the printer settings (the vulnerability requires this feature to be active).
-
Assess network accessibilityConfirm the printer IP address is reachable from other devices on your network segment. Attempt a ping test or TCP connection to the printer IP on port 80/443. If the printer is isolated on a restricted VLAN with no untrusted access, the attack surface is reduced.Affected if The printer is directly accessible from the same network segment where untrusted or guest devices can operate.
Your environment is affected if you have any of the eight listed Canon printer models running firmware version 06.02 or earlier, with XPS or PostScript processing enabled, and the device is accessible from your network segment.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate affected Canon printer models to firmware v06.03 or later. If firmware updates are unavailable, isolate affected devices on restricted network segments and disable unnecessary XPS/PostScript processing capabilities.
Any Canon firmware version newer than 06.02 (contact Canon support or visit the Canon security advisory for exact fixed version number)
- Identify the specific Canon printer model from the affected product list (Mf656cdw, Mf653cdw, Mf652cw, Mf1238 Ii, Mf1643if Ii, Mf1643i Ii, Lbp237dw, Lbp236dw)
- Navigate to Canon's official support site for your region (canon.jp, usa.canon.com, canon-europe.com, or psirt.canon)
- Locate the firmware download section for your specific printer model
- Download the firmware update version newer than 06.02
- Follow Canon's standard firmware update procedure, typically involving: a) Downloading the firmware file to a computer, b) Connecting the printer to the computer via USB or network, c) Using Canon's firmware update utility or web interface to apply the update, d) Power cycling the printer to complete the installation
- Verify the firmware version has been updated to a version greater than 06.02
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14235 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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