# CVE-2025-14235: Memory corruption in 1238P II

> A buffer overflow in XPS font processing allows network attackers to execute arbitrary code or cause denial of service on affected Canon printers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-wcv5-68f6-32pr

## What is CVE-2025-14235?

CVE-2025-14235 is a critical memory corruption vulnerability in Canon Inc. 1238P II, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-14235?

It affects 16 products.


Products: Canon Lbp1238 Ii Firmware, Canon Lbp236dw Firmware, Canon Lbp237dw Firmware, Canon Lbp632cdw Firmware, Canon Lbp633cdw Firmware, Canon Mf1238 Ii Firmware, Canon Mf1643i Ii Firmware, Canon Mf1643if Ii Firmware, Canon Mf451dw Firmware, Canon Mf452dw Firmware, Canon Mf453dw Firmware, Canon Mf455dw Firmware, Canon Mf652cw Firmware, Canon Mf653cdw Firmware, Canon Mf654cdw Firmware, Canon Mf656cdw Firmware.

## How do I fix CVE-2025-14235?

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

## Is CVE-2025-14235 being exploited?

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

## Other vulnerabilities in Canon Inc. 1238P II

- [CVE-2024-12647](https://insights.sbomify.com/CVE-2024-12647/): Memory corruption in Color imageCLASS LBP632Cdw (critical 9.8)
- [CVE-2024-12648](https://insights.sbomify.com/CVE-2024-12648/): Memory corruption in Color imageCLASS LBP632Cdw (critical 9.8)
- [CVE-2024-12649](https://insights.sbomify.com/CVE-2024-12649/): Memory corruption in Color imageCLASS LBP632Cdw (critical 9.8)
- [CVE-2025-14231](https://insights.sbomify.com/CVE-2025-14231/): Memory corruption in 1238P II (critical 9.3)
- [CVE-2025-14232](https://insights.sbomify.com/CVE-2025-14232/): Memory corruption in 1238P II (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14235 and fix it if it is affected.

What it is: CVE-2025-14235 is a critical memory corruption vulnerability in Canon Inc. 1238P II, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14235 in the wild and no public exploit code.

Affected product: Canon Inc. 1238P II. 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-2025-14235/ (Markdown: https://insights.sbomify.com/CVE-2025-14235/index.md)
```

## Sources

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

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