CVE-2026-32679
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 · uneditedThe installers of LiveOn Meet Client for Windows (Downloader5Installer.exe and Downloader5InstallerForAdmin.exe) and the installers of Canon Network Camera Plugin (CanonNWCamPlugin.exe and CanonNWCamPluginForAdmin.exe) insecurely load Dynamic Link Libraries (DLLs). If a malicious DLL is placed at the same directory, the affected installer may load that DLL and execute its code with the privilege of the user invoking the installer.
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 confidenceThe LiveOn Meet Client and Canon Network Camera Plugin Windows installers are vulnerable to DLL hijacking. The installers use insecure DLL search paths, allowing an attacker who can place a malicious DLL in the same directory as the installer to achieve code execution with the privileges of the user running the installer.
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= 1.0.0.0= 1.0.0.0= 1.0.0.0= 1.0.0.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Locate affected installer filesSearch the file system for files matching these names: Canonnwcamplugin.exe, Canonnwcampluginforadmin.exe, Downloader5installer.exe, Downloader5installerforadmin.exe. Check typical installation directories, download folders, and temporary directories.Affected if Any of these four executables are found on the system with version 1.0.0.0
-
Verify installer versionRight-click each found executable, select Properties, and examine the File version field on the Details tab. Alternatively, run: Get-Item "path\to\executable" | Format-List *Affected if The File version shows exactly 1.0.0.0 for any of the affected installer executables
-
Check directory writabilityRight-click the folder containing the installer, select Properties, then Security tab. Verify which users or groups have Write or Modify permissions. Alternatively, run: Get-Acl "path\to\directory" | Select-Object -ExpandProperty AccessAffected if The directory containing the installer grants Write or Modify permissions to users other than the installer owner (such as Users, Authenticated Users, or Everyone)
-
Inspect for suspicious DLLsList all DLL files in the same directory as the installer: Get-ChildItem "path\to\installer\directory" -Filter *.dllAffected if Unexpected or unrecognized DLL files exist in the directory alongside the installer, especially DLLs not belonging to the installer package
You are affected if any of the four installer executables with version 1.0.0.0 exist on your system and are stored in a directory writable by other users.
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.
From vendor dataUsers should ensure the directory from which the installer is run is not writable by unprivileged users and contains no untrusted files. The vendor (Canon) must release patched installers that use secure DLL loading practices (e.g., safe DLL search mode, absolute paths).
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32679 — 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-2026-32679 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