# CVE-2025-14946: Libnbd: libnbd: arbitrary code execution via ssh argument injection through a malicious uri

> A malicious URI can inject SSH arguments in libnbd, allowing arbitrary code execution with user privileges.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-14946, GHSA-mcgc-vc2p-cf7x, UBUNTU-CVE-2025-14946, openSUSE-SU-2025:15842-1

## What is CVE-2025-14946?

CVE-2025-14946 is a medium-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 19 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in libnbd. A malicious actor could exploit this by convincing libnbd to open a specially crafted Uniform Resource Identifier (URI). This vulnerability arises because non-standard hostnames starting with '-o' are incorrectly interpreted as arguments to the Secure Shell (SSH) process, rather than as hostnames. This could lead to arbitrary code execution with the privileges of the user running libnbd.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libnbd` | openSUSE:Tumbleweed | All versions | 1.24.0-2.1 |

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

Apply the vendor's patch.

## Is CVE-2025-14946 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14946 is a medium-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 19 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14946 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-14946/ (Markdown: https://insights.sbomify.com/CVE-2025-14946/index.md)
```

## Sources

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

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