CVE-2025-61984

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)

Published: 2025-10-06 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-61984 is rated Low Risk (19/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.22%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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-61984

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 2026-06-15 0.01% 0.22% +0.21%
2 2025-10-07 — 0.01% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.6 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:N)
Service keeps running; no real outage angle.
 1.0 2.5 [email protected]

Weakness enumeration for CVE-2025-61984

OS Trackers for CVE-2025-61984

vendor priority summary link
alpine low CVE-2025-61984: 1 source package rows (openssh); 70 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 2, open 68. https://security.alpinelinux.org/vuln/CVE-2025-61984
debian not yet assigned CVE-2025-61984 not yet assigned priority: Debian including 1 source packages (openssh), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-61984
redhat medium — https://access.redhat.com/security/cve/CVE-2025-61984
suse medium CVE-2025-61984 severity moderate: SUSE including 345 source package names (2.0.4-5.5.405:openssh-8.4p1-150300.3.57.1, 2.0.4-5.5.405:openssh-clients-8.4p1-150300.3.57.1, …), 1549 product×package rows across 301 product lines (Container suse/manager/4.3/proxy-ssh, Container suse/manager/5.0/x86_64/proxy-ssh, … (301 product lines)): Fixed 1310, Known Affected 231, First Fixed 8. https://www.suse.com/security/cve/CVE-2025-61984/
ubuntu low CVE-2025-61984 low priority: Ubuntu including 2 source packages (openssh, openssh-ssh1), 16 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): ignored 8, released 5, needed 3. https://ubuntu.com/security/CVE-2025-61984

Affected software / configurations for CVE-2025-61984

Vendor Product Version Raw CPE
openbsd openssh < 10.1 cpe:2.3:a:openbsd:openssh:*:*:*:*:*:*:*:*

References for CVE-2025-61984

cvelogic Threat Intelligence