CVE-2025-14946: Red Hat libnbd · Argument Injection
Affects Red Hat libnbdSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Red Hatredhat/libnbdpkg:rpm/redhat/libnbdOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-14946, organizations should: 1) Monitor for updates and apply patches from Red Hat or libnbd maintainers as soon as they become available to ensure proper input sanitization and argument handling. 2) Implement strict input validation and sanitization on all URIs passed to libnbd, rejecting or sanitizing hostnames that begin with argument-like prefixes such as '-o'. 3) Restrict libnbd usage to trusted users and environments, minimizing exposure to untrusted or malicious inputs. 4) Employ application whitelisting or command-line argument filtering to prevent injection of unauthorized SSH arguments. 5) Audit and monitor logs for unusual SSH command invocations or libnbd usage patterns indicative of exploitation attempts. 6) Limit privileges of users running libnbd to the minimum necessary to reduce the impact of potential code execution. 7) Educate users and administrators about the risks of processing untrusted URIs with libnbd. 8) Consider network segmentation to isolate systems running libnbd from untrusted networks or users. These measures, combined with timely patching, will reduce the risk of exploitation and limit potential damage.
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.