# CVE-2026-82689: D-Link DNS-320L/DNS-327L/DNS-340L/DNS-345 ISO Image isomount_mgr.cgi os command injection

> Remote attackers can execute arbitrary OS commands via the upIsoRootPath argument in the ISO Image Handler CGI script on affected D-Link NAS devices.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-48gx-r96g-wf4f

## What is CVE-2026-82689?

CVE-2026-82689 is a critical command injection vulnerability in D-Link DNS-320L, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in D-Link DNS-320L, DNS-327L, DNS-340L and DNS-345 up to 20260717. Affected is an unknown function of the file /cgi-bin/isomount_mgr.cgi of the component ISO Image Handler. The manipulation of the argument upIsoRootPath results in os command injection. The attack can be executed remotely. The exploit is now public and may be used.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-82689 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82689 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82689 is a critical command injection vulnerability in D-Link DNS-320L, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82689 exists.

Affected product: D-Link DNS-320L. 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-82689/ (Markdown: https://insights.sbomify.com/CVE-2026-82689/index.md)
```

## Sources

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

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