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

CVE-2026-6891

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 My Image Garden for macOS Version 3.6.8 or earlier may allow a local attacker with login privileges to exploit a specially crafted symbolic link during installation to modify permissions of files for which they would not normally have authorization.

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 · moderate confidence

This is a local privilege escalation vulnerability in the My Image Garden installer for macOS. The installer improperly handles symbolic links during the installation process, allowing a local authenticated attacker to create a malicious symlink that, when processed during installation, can modify permissions on files outside the intended installation directory.

MitigationUpdate to My Image Garden version 3.6.9 or later. If immediate updating is not possible, ensure the installer is only run in trusted environments and verify installer integrity via checksums before execution.

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. Check if My Image Garden is installed
    Run 'ls /Applications/ | grep -i "My Image Garden"' in Terminal to see if the application exists in the Applications folder, or check ~/Applications for user-installed copies.
    Affected if The application exists in the system
  2. Identify the installed version
    Right-click My Image Garden.app in Finder, select 'Get Info', and read the version number under 'Kind' or 'Version', or run 'mdls -name kCFBundleShortVersionString "/Applications/My Image Garden.app"' in Terminal.
    Affected if The displayed version is 3.6.8 or earlier, or the version cannot be determined (unknown versions should be treated as vulnerable)
  3. Check for recent installation activity
    Review system logs around installation times using 'log show --predicate 'subsystem == "com.apple.installer"' --last 30d | grep -i "My Image Garden"' to identify recent installs.
    Affected if An installer for version 3.6.8 or earlier was recently run on this system
  4. Audit for suspicious symlinks in installation directories
    Run 'ls -la /private/var/folders/*/C/ 2>/dev/null | grep "^l"' and 'find /tmp -type l -ls 2>/dev/null' to look for symlinks that may have been created by the installer outside the intended target directory.
    Affected if Symlinks exist in temporary or staging directories pointing outside /Applications or the intended install path

If My Image Garden version 3.6.8 or earlier is installed, or if the version cannot be confirmed and the software is present, the environment is likely affected by this vulnerability.

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

Update to My Image Garden version 3.6.9 or later. If immediate updating is not possible, ensure the installer is only run in trusted environments and verify installer integrity via checksums before execution.

Recommended fix Moderate confidence

My Image Garden for macOS version later than 3.6.8 (e.g., the latest version available from Canon)

  1. Check the currently installed version of My Image Garden for macOS (e.g., via the Applications folder or the About dialog).
  2. Visit the official Canon support website for My Image Garden for macOS and navigate to the download page for your region.
  3. Download the most recent version of My Image Garden for macOS that is newer than version 3.6.8.
  4. Run the downloaded installer and follow the on-screen instructions to complete the installation.
  5. After installation, verify that the version has been updated to the new release (e.g., open My Image Garden and check the About dialog).

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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