# CVE-2026-103665: The installer for Yamaha LAN Monitor for Windows provided by Yamaha Corporation may insecurely load Dynamic Link Libraries (DLLs).


- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-wx4r-57mg-fmh2

## What is CVE-2026-103665?

CVE-2026-103665 is a high-severity vulnerability in Yamaha LAN Monitor for Windows, published on 29 Oct 2026. 

### Official description

The installer for Yamaha LAN Monitor for Windows provided by Yamaha Corporation may insecurely load Dynamic Link Libraries (DLLs). When the installer is launched in a directory containing a specially crafted DLL file, the malicious DLL may be loaded, resulting in arbitrary code execution with administrative privileges.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-103665?


## How do I fix CVE-2026-103665?

No fix has been published for CVE-2026-103665 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103665 being exploited?

There is no known exploitation of CVE-2026-103665 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103665 and fix it if it is affected.

What it is: CVE-2026-103665 is a high-severity vulnerability in Yamaha LAN Monitor for Windows, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103665 in the wild and no public exploit code.

Affected product: Yamaha LAN Monitor for Windows. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103665/ (Markdown: https://insights.sbomify.com/CVE-2026-103665/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103665
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103665
- OSV: https://osv.dev/vulnerability/CVE-2026-103665

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103665/
Summaries are generated and may contain mistakes; the official description above is the record.