dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2026-6892

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
50/100
Remediation priority · Moderate

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
Improper handling of symbolic links in the installer of CUPS Printer Driver for macOS(*) may allow a local attacker with login privileges to exploit a specially crafted symbolic link during installation to modify permissions of directories for which they would not normally have authorization.  *:Canon PIXUS iX6800 Series CUPS Printer Driver for macOS Version 16.91.0.0 or earlier (Japan) Canon PIXMA MG2500 Series and iX6800 Series CUPS Printer Driver for macOS Version 16.91.0.0 or earlier (US and 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

The Canon CUPS Printer Driver installer for macOS fails to properly validate symbolic links during the installation process. A local attacker with login privileges can create a specially crafted symlink that the installer will follow, allowing modification of permissions on directories outside the intended installation scope.

MitigationApply vendor patch when available; until then, avoid running the installer in untrusted multi-user environments and ensure only trusted users have write access to installation directories.

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Locate Canon CUPS Printer Driver installation
    Check for Canon printer driver packages in /Library/Printers/Canon/, /Applications/Canon/, or via `ls /Library/Printers/` and `pkgutil --packages | grep -i canon`
    Affected if Canon CUPS Printer Driver software is present on the system
  2. Identify installed driver version
    Use `pkgutil --info $(pkgutil --packages | grep -i canon | head -1)` to query the installed package version, or check the driver application's Info.plist for version strings
    Affected if The installed version cannot be verified as patched or falls within an unpatched release range
  3. Verify installer component presence
    Check for Canon installer packages in /Library/Receipts/ or examine /Library/Application Support/Canon/ for installation-related files and scripts
    Affected if Installer components from Canon CUPS driver are found on the system
  4. Confirm multi-user environment exposure
    Review system configuration for multiple user accounts via `dscl . -list /Users` and check if non-privileged users have access to the system
    Affected if The system hosts multiple user accounts and the Canon driver installer has been run with elevated privileges
  5. Audit directory permissions post-installation
    Run `ls -la /Library/Printers/` and examine anyCanon-related directories for unusual permission changes or symlink artifacts
    Affected if Unexpected symlinks or modified permissions exist in Canon-related directories

A user is affected if the Canon CUPS Printer Driver for macOS is installed and the installer was executed in an environment where untrusted local users could have exploited the symlink validation flaw to escalate privileges via directory permission manipulation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; until then, avoid running the installer in untrusted multi-user environments and ensure only trusted users have write access to installation directories.

Recommended fix Moderate confidence

Latest version available on Canon support website (newer than 16.91.0.0)

  1. 1. Navigate to the Canon support website for your region (canon.jp, www.canon-europe.com, or www.usa.canon.com)
  2. 2. Search for your specific printer model (PIXUS iX6800 Series, PIXMA MG2500 Series, or iX6800 Series)
  3. 3. Locate the CUPS Printer Driver for macOS section
  4. 4. Download the latest available version of the driver
  5. 5. Uninstall the current Canon CUPS Printer Driver from your Mac before installing the new version
  6. 6. Install the updated driver following Canon's installation instructions

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6892 — 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-2026-6892 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