How to Fix CVE-2026-32679: Uncontrolled Search Path Element in Downloader5Installer.exe
By Sai Kiran Pandrala
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-36941: SQL injection in Sourcecodester Online — SQL injection in Sourcecodester Online
- How to Fix CVE-2026-32024: OpenClaw < 2026.2.22 - Symlink Traversal in Avatar Handling in OpenClaw — OpenClaw < 2026.2.22 - Symlink Traversal in Avatar Handling in OpenClaw
- How to Fix CVE-2026-2179: SQL Injection in Hospital Management System , SQL Injection in Hospital Management System
- How to Fix CVE-2026-23873: Path Traversal in hustoj , Path Traversal in hustoj
- How to Fix CVE-2026-0567: SQL Injection in Content Management System , SQL Injection in Content Management System
Last verified: 2026-05-25
CVE-2026-32679 is a uncontrolled search path element in Japan Media Systems Corporation Downloader5Installer.exe. Fix it by upgrading to the patched build from the vendor advisory.
| Severity | CVSS 8.4 - High |
|---|---|
| Actively exploited? | Not currently in the CISA KEV catalog |
| Affected | Downloader5Installer.exe Ver.1.0.0.0; Downloader5InstallerForAdmin.exe Ver.1.0.0.0; CanonNWCamPlugin.exe Ver.1.0.0.0; CanonNWCamPluginForAdmin.exe Ver.1.0.0.0 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-427: Uncontrolled Search Path Element |
What is CVE-2026-32679?
CVE-2026-32679 is a uncontrolled search path element flaw in Japan Media Systems Corporation Downloader5Installer.exe. It carries a CVSS base score of 8.4 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
From the source record: The 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.
Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.
Am I affected?
You are affected if your installation of Downloader5Installer.exe matches a version listed in the Affected row above.
Check the running version against the Affected row above using the product's admin console or --version flag.
How to fix CVE-2026-32679
Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for Downloader5Installer.exe.
Generic upgrade pattern
If the affected product is a Linux package, upgrade via the system package manager:
# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y
# RHEL / Rocky / Alma
sudo dnf upgrade --security -y
If it ships as a Windows installer, download the patched build from the vendor advisory and:
# Vendor advisory: https://web.liveon.ne.jp/wp-content/uploads/2026/04/JMSSA2026-001.pdf
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion
After applying the patch
- Restart the service or device so the patched binary loads.
- Confirm the running version matches the Fixed in row using the verification command below.
- Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.
If you can't patch immediately
Until the patch lands, narrow the attack surface with these runnable controls.
Restrict network exposure
Block public access to the affected service at the perimeter. Allow only trusted source IPs.
# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
-RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny" -Direction Inbound -Action Block `
-Protocol TCP -LocalPort 443
Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.
How to verify the fix worked
Confirm the patched build is the one actually running.
Check the running version against the Affected row above using the product's admin console or --version flag.
Expected: a version at or above the patched build named in the vendor advisory.
Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.
Frequently asked questions
Is CVE-2026-32679 being exploited in the wild?
As of 2026-05-25, CVE-2026-32679 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.
What is the CVSS score for CVE-2026-32679?
The CVSS base score is 8.4 (High).
What version fixes this?
The vendor advisory names the patched build. See the References section.
Will a WAF or IDS rule alone close this?
No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.
References
- Official vendor advisory: https://web.liveon.ne.jp/wp-content/uploads/2026/04/JMSSA2026-001.pdf
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-32679
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://jvn.jp/en/jp/JVN45563482/
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*