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

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.

Published: 2025-12-19 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-14946 is rated Low Risk (20.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-14946

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-20 0.02%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-14946

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
1.3 3.4 [email protected]

Weakness enumeration for CVE-2025-14946

OS Trackers for CVE-2025-14946

vendor priority summary link
alpine CVE-2025-14946: 1 source package rows (libnbd); 6 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 6. https://security.alpinelinux.org/vuln/CVE-2025-14946
debian unimportant CVE-2025-14946 unimportant priority: Debian including 1 source packages (libnbd), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-14946
redhat medium https://access.redhat.com/security/cve/CVE-2025-14946
suse high CVE-2025-14946 severity important: SUSE including 22 source package names (containerized-data-importer, containerized-data-importer-api, …), 88 product×package rows across 29 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (29 product lines)): Known Not Affected 82, Fixed 6. https://www.suse.com/security/cve/CVE-2025-14946/
ubuntu medium CVE-2025-14946 medium priority: Ubuntu including 1 source packages (libnbd), 6 status rows across 6 suites (focal, jammy, noble, plucky, questing, upstream): needs-triage 4, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-14946

Affected software / configurations for CVE-2025-14946

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-14946

cvelogic Threat Intelligence