# CVE-2025-66002: Local users can perform arbitrary unmounts via smb4k mount helper due to lack of input validation

> Local attackers can execute arbitrary unmount commands via argument injection in the smb4k mount helper, potentially escalating privileges or disrupting services.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-66002, GHSA-g8f7-f2vp-fv6x, UBUNTU-CVE-2025-66002

## What is CVE-2025-66002?

CVE-2025-66002 is a medium-severity command injection vulnerability in https://github.com/KDE/ smb4k, published on 8 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An  Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability allows local users ton perform arbitrary unmounts via smb4k mount helper

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2025-66002?


## How do I fix CVE-2025-66002?

Apply the vendor's patch.

## Is CVE-2025-66002 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66002 and fix it if it is affected.

What it is: CVE-2025-66002 is a medium-severity command injection vulnerability in https://github.com/KDE/ smb4k, published on 8 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66002 in the wild and no public exploit code.

Affected product: https://github.com/KDE/ smb4k. 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-2025-66002/ (Markdown: https://insights.sbomify.com/CVE-2025-66002/index.md)
```

## Sources

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

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