Out-of-bounds WriteWeakness · CWE-787

CVE-2025-1268

CRITICAL · 9.4 CVSS v3.1 Published 2025-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Out-of-bounds vulnerability in EMF Recode processing of Generic Plus PCL6 Printer Driver / Generic Plus UFR II Printer Driver / Generic Plus LIPS4 Printer Driver / Generic Plus LIPSLX Printer Driver / Generic Plus PS Printer Driver / Generic FAX Printer Driver / UFRII LT Printer Driver / CARPS2 Printer Driver / PDF Driver / LIPS4 Printer Driver / LIPSLX Printer Driver / UFR II Printer Driver / PS Printer Driver / PCL6 Printer Driver

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

An out-of-bounds memory access vulnerability exists in the EMF (Enhanced Metafile) Recode processing component of multiple Canon printer drivers. This flaw in the metafile parsing logic could allow an attacker to execute arbitrary code or cause a denial of service by sending specially crafted print jobs to affected devices.

MitigationApply vendor-supplied driver updates from Canon for all affected printer models. In enterprise environments, prioritize patching remote/exposed print servers and network printers, and consider network segmentation to limit exposure to untrusted print traffic.

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

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
Low

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

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 Canon printer drivers on the system
    Open Device Manager, expand 'Print queues', or check Programs and Features for Canon printer driver packages. On Windows, also check C:\Windows\System32\spool\drivers\x64\ for Canon driver files (*.sys, *.dll).
    Affected if Canon printer drivers are installed on the system
  2. Determine the installed Canon driver version
    Right-click the Canon printer in Device Manager, select Properties, then the Driver tab. Alternatively, right-click the driver DLL in the spooler folder and view Properties > Details > File version.
    Affected if The driver version falls within the affected version range or cannot be determined to be patched
  3. Verify the EMF print processor is in use
    Open Services > Print Spooler, note the executable path. Run 'printmanagement.msc' > Print Servers > Server Properties > Drivers. Select the Canon driver and check which print processor is associated, or run 'wmic printjob get /format:list' to see active jobs.
    Affected if The system uses the standard Windows EMF print processor or a Canon EMF-related processing component
  4. Confirm print job submission accepts untrusted sources
    Check if the print spooler is exposed to network or guest users. Review printer sharing settings and any direct IP printing ports (ports 9100, 631). Query registry HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors for USB/RAW ports that accept external jobs.
    Affected if The printer or print spooler accepts jobs from untrusted network sources or unauthenticated users

The environment is affected if Canon printer drivers are installed, the driver version is unpatched, and the system processes EMF print jobs from potentially untrusted sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied driver updates from Canon for all affected printer models. In enterprise environments, prioritize patching remote/exposed print servers and network printers, and consider network segmentation to limit exposure to untrusted print traffic.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1268 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1268 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