SSH
Monthly
Command injection in the NetBird desktop client (versions 0.60.0 through 0.74.6) lets a malicious or compromised peer inject arbitrary OpenSSH directives - including command-executing ones - into the system-wide drop-in config of other clients' Linux, macOS, Windows and FreeBSD hosts. Exploitation requires the attacker to control an enrolled peer whose crafted FQDN or hostname containing a double quote is distributed to the victim, and the injected command runs only when a local user subsequently invokes ssh, so peer membership plus a local user action are both prerequisites rather than an unauthenticated internet-facing attack. NetBird 0.74.7 fixes the issue by rejecting peer names that are not valid DNS names; no public exploit identified at time of analysis, and the Android and iOS apps are not affected.
Remote code execution in OpenSSH for Windows (the Microsoft OpenSSH server component) can be triggered over the network by an unauthenticated attacker with no user interaction, according to the CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N and a 9.8 base score. The flaw is a use-after-free that can lead to memory corruption and potential code execution or denial of service, but exposure is limited to Windows hosts where the optional OpenSSH Server feature is installed and listening, typically on TCP/22. No public exploit identified at time of analysis, and confidence is limited by single-source reporting; defenders should treat any network-exposed Windows sshd listener as high risk and restrict or firewall the SSH port pending patching.
Local privilege escalation in OpenSSH for Windows allows an authenticated attacker to elevate privileges by triggering a double-free memory corruption. Affected builds include Windows 10, Windows 11, and Windows Server versions prior to the fixed builds listed in Microsoft's advisory. No public exploit identified at time of analysis; a vendor-released patch is available.
Heap-based buffer overflow in OpenSSH for Windows can let an unauthenticated network attacker execute code, but the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H and the independent assessment indicate the victim must initiate the vulnerable SSH operation, likely by using an affected Windows OpenSSH client against an attacker-controlled or compromised SSH server. Affected builds span Windows 10, Windows 11, and Windows Server 2019, 2022, and 2025 as enumerated in EUVD-2026-99587; Microsoft has released patched builds through the MSRC update guide. No public exploit identified at time of analysis, and CISA SSVC marks exploitation as none and Automatable as no, so risk is gated by user interaction and the need for the victim to connect to attacker-influenced infrastructure.
Relative path traversal in OpenSSH for Windows (CWE-23) can allow an unauthenticated remote attacker to escape intended directories during an SSH interaction and, ultimately, execute code on the affected host - carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and rated by SSVC as having total technical impact. Exploitation is not attacker-autonomous: it requires the victim to use the OpenSSH for Windows component and to initiate or accept an SSH connection to an attacker-controlled or compromised endpoint (the UI:R user-interaction requirement), and the host must be running a build below its fixed release (for example Windows 11 24H2 below 10.0.26100.9711 or Windows Server 2022 below 10.0.20348.5761). Current intelligence shows no public exploit identified at time of analysis, SSVC exploitation status of 'none', and non-automatable delivery, so this is a high-priority-on-paper issue whose real-world urgency is tempered by the lack of confirmed exploitation - vendor patches are available per the Microsoft advisory and should still be prioritized.
A heap-based buffer overflow in the OpenSSH for Windows component allows an authenticated local attacker with a low-privileged account to elevate privileges on the affected host, with high attack complexity required to reliably shape the heap for exploitation. Affected systems are Windows 10, Windows 11 and Windows Server 2019/2022/2025 installations whose OpenSSH component predates Microsoft's patched builds (for example, Windows 11 24H2/25H2 <10.0.26100.9711 and <10.0.26200.9711, Windows Server 2025 <10.0.26100.33650); updated builds are not exploitable. No public exploit code has been identified at time of analysis and Microsoft has released fixes, but the 7.0 CVSS score reflects full confidentiality, integrity and availability impact if the overflow is successfully turned into code execution; this is a genuine but second-tier local privilege-escalation issue rather than a remotely wormable flaw, and there is no confirmed active exploitation (no CISA KEV listing).
Local privilege escalation in OpenSSH for Windows stems from a use-after-free (CWE-416) in the SSH component shipped with supported Windows builds, allowing an authenticated low-privileged user who already holds a foothold on the host to corrupt memory inside the OpenSSH process and elevate to the privileges of that process, with high impact across confidentiality, integrity and availability (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is strictly local: there is no remote or network vector, no user interaction is required, and exploitation presupposes a valid low-privilege account plus the vulnerable OpenSSH for Windows component being installed and in use on an unpatched build. No public exploit code has been identified at the time of analysis, CISA's SSVC decision framework records exploitation as none and the flaw as not automatable, and Microsoft has released vendor patches for all affected Windows versions.
Heap-based buffer overflow in OpenSSH for Windows - the optional OpenSSH client/server component shipped with Windows 10, Windows 11, and Windows Server 2019/2022/2025 - can allow code execution in the context of the vulnerable process, with the CVSS v3.1 vector AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H (reported score 7.5) reflecting full confidentiality, integrity and availability impact. Exploitation is unauthenticated (PR:N) but is gated by two concrete limiters: User Interaction is Required (UI:R), implying a victim must actively initiate or accept the vulnerable SSH operation rather than being hit passively, and Attack Complexity is High (AC:H), meaning the attacker must satisfy a non-trivial precondition such as a specific heap or memory layout. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA SSVC Exploitation: none; KEV: no), and CISA's SSVC also rates the flaw as not automatable, although technical impact is assessed as total - on balance the signals point to a serious-but-not-emergency priority for hosts running the OpenSSH feature.
Denial of service in the OpenSSH server component (sshd) shipped as an optional feature of Windows allows an unauthenticated, remote attacker who can reach the SSH port to consume host resources without throttling, degrading or exhausting the service so legitimate SSH sessions can no longer be established. Only Windows builds that actually have the OpenSSH Server capability installed, enabled and network-reachable are at risk - the feature is not on by default for most client installs, which materially narrows the attack surface, and the impact is availability-only (C:N/I:N/A:H). The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5), CISA's SSVC assessment records exploitation as none, automatable as yes and technical impact as partial, and there is no public exploit identified at time of analysis; a vendor fix is available.
Command injection in the OpenSSH ssh client before version 10.6 occurs when a username supplied on the command line contains a '$' or '\' character, which is not correctly escaped or quoted and can be interpreted as shell syntax. The flaw is assessed as CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and requires the victim to invoke ssh with an attacker-controlled username - for example from a crafted ssh:// URI, a shared connection string, or a script or alias - so it is not remotely triggerable against a default server. No public exploit was identified at time of analysis, EPSS is 0.13% (2nd percentile), and the issue does not appear on CISA KEV; this is a genuine but not emergency-grade issue, and patched clients (10.6 and later) are unaffected.
OpenSSH sshd before 10.6 can incorrectly persist GSSAPIAuthentication state across authentication attempts when GSSAPIAuthentication is enabled, allowing a remote, unauthenticated attacker to influence authentication integrity on the same connection. This is a non-default configuration issue: stock OpenSSH deployments without Kerberos/GSSAPI are not affected, and the attacker must drive a sequence of authentication attempts (high attack complexity). No public exploit code has been identified, EPSS is very low (0.08%, 0th percentile), and CISA SSVC reports no exploitation; the vendor has released a fix in OpenSSH 10.6.
Credentials can incorrectly persist after a failed GSSAPIAuthentication attempt in the sshd daemon of OpenSSH before 10.6, allowing an authentication context that should have been discarded to remain usable and potentially granting access under another identity (CWE-669, integrity impact). Only hosts that explicitly enable GSSAPIAuthentication are affected, since the OpenSSH default is 'no', so exposure is largely limited to Kerberos/GSSAPI-integrated environments; the flaw is fixed in OpenSSH 10.6. No public exploit code has been identified at time of analysis, EPSS is negligible (0.08%), and CISA SSVC records no observed exploitation and rates the issue as non-automatable with partial technical impact, so real-world risk is moderate despite the 7.5 'High' base score.
A partial authentication bypass in Apache MINA SSHD lets a remote attacker satisfy a repeated-public-key multi-authentication policy by presenting the same public key twice, so a server configured to demand two distinct keys can be entered with only one of them. Affected are versions before 2.20.0 and 3.0.0-M1 through 3.0.0-M5 of the sshd-core component; the vendor assigns CVSS 3.1 8.1 (High, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), where PR:L reflects that the attacker must already legitimately possess at least one accepted key pair. Exploitation is confined to the non-default hardened configuration that requires repeated/multiple public keys (the equivalent of OpenSSH's AuthenticationMethods "publickey,publickey"); single-key or password-based deployments are not affected, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Use-after-free in Microsoft's OpenSSH for Windows enables unauthenticated network attackers to achieve remote code execution across a broad range of Windows 10, Windows 11, and Windows Server releases. The CVSS vector (AV:N/AC:H/PR:N/UI:R) indicates exploitation is constrained by high attack complexity and a requirement for user interaction, consistent with a client-side attack path where a victim must connect to an attacker-controlled SSH endpoint. Microsoft has released patched builds across all affected Windows versions; no public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in SSH.NET's ScpClient.Download() enables a malicious, compromised, or man-in-the-middle SCP server to write arbitrary files anywhere the client process has write access during recursive directory downloads. All SSH.NET NuGet package versions up to and including 2025.1.0 are affected; the vulnerability is analogous to CVE-2019-6111 in OpenSSH but extends to directory traversal. No public exploit code or CISA KEV listing has been identified at time of analysis, though the integrity impact is high given the file-write primitive can overwrite SSH authorized keys, shell rc files, or application binaries.
Path traversal in rclone's `serve restic` REST API allows any attacker with network access to the endpoint to read, create, overwrite, or delete objects outside the operator-configured backend directory. The flaw spans rclone v1.40 through v1.74.4 and affects WebDAV, FTP, SFTP, HTTP, and Memory backends - but not S3-compatible or local filesystem backends, which encode `..` as literal filename characters. A fully functional, step-by-step proof of concept has been publicly released; no CISA KEV listing exists at time of analysis.
Command-restriction bypass in Apache MINA SSHD (server-side) lets a user who authenticates with an OpenSSH user certificate carrying a force-command directive execute arbitrary commands instead of the single restricted command the certificate authority intended. The server accepts and honors such certificates but silently ignores the force-command and verify-required options, breaking the security model that certificate issuers rely on to constrain principals. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw is confirmed and fixed by the Apache Software Foundation in versions 2.19.0 and 3.0.0-M5.
Argument injection in bosh-cli versions before v7.10.4 lets a compromised or malicious BOSH Director inject arbitrary OpenSSH command-line options into the ssh process that the CLI spawns locally, achieving code execution on the operator's own workstation. It triggers during non-interactive SSH paths such as bosh ssh -c, bosh logs -f, and similar flows where the CLI builds an ssh command from Director-supplied data. No public exploit is identified at time of analysis, and it is not listed in CISA KEV; the CVSS 4.0 base score is 7.7 (High).
Memory corruption in the OpenSSH client (ssh) before 10.4 lets a malicious or compromised SSH server trigger a use-after-free on the connecting client by changing its host key during a key re-exchange (rekey), potentially leading to information disclosure or code execution in the client process. Only the client side is affected; the server is not vulnerable. There is no public exploit identified at time of analysis and it is not on CISA KEV, and EPSS is low (0.25%, 16th percentile), but the flaw is fixed in OpenSSH 10.4/10.4p1.
Denial of service in OpenSSH sshd before 10.4 lets remote unauthenticated attackers exhaust server resources by driving excessive authentication attempts, because the MaxAuthTries cap was not correctly enforced for the GSSAPIAuthentication path. Only deployments that have enabled GSSAPI-based authentication are exposed, and there is no public exploit identified at time of analysis. EPSS is low (0.34%, 26th percentile) and CISA SSVC records no observed exploitation, so this is a real but non-urgent availability issue rather than a code-execution threat.
Security-control bypass in OpenSSH sshd before 10.4 causes the DisableForwarding=yes hardening directive to be silently ignored when PermitTunnel=yes is also set, so tun-device forwarding remains available despite an administrator's explicit policy to disable all forwarding. Affected operators are those who rely on DisableForwarding as a defense-in-depth restriction; the flaw lets an authenticated user establish layer-2/3 tunnels the configuration was meant to forbid. There is no public exploit identified at time of analysis, EPSS is low (0.13%, 3rd percentile), and it is not on CISA KEV.
Remote denial-of-service in russh, a Rust implementation of the SSH protocol, allows unauthenticated remote attackers to exhaust server memory by sending small compressed SSH packets that inflate to massive sizes post-decompression. Affecting all versions from 0.34.0 through 0.61.0, the flaw stems from missing post-decompression size enforcement in Decompress::decompress(), allowing payloads under the 256 KiB wire cap to expand beyond 128 MiB. No public exploit identified at time of analysis, but the advisory includes a detailed PoC demonstrating pre-authentication exploitation against default server configurations.
SSH public-key authentication bypass in AsyncSSH 2.22.0 (Python pip package) allows remote attackers to log in as another identity when the server uses the OpenSSH-style per-user pattern 'AuthorizedKeysFile authorized_keys/%u'. Because the %u token is expanded from the raw SSH username without rejecting '/', '\', or '..', an attacker supplying a traversal username (e.g. '../../../attacker.pub') forces the server to read an authorized-keys file outside the intended directory; if that file contains the attacker's public key, authentication succeeds. Publicly available proof-of-concept exploit code exists (harness plus exploit script in the advisory), but there is no public exploit identified as being used in the wild and the issue is not in CISA KEV; EPSS is low at 0.22%.
Authentication bypass in the Go x/crypto/ssh library (versions before 0.52.0) allows SSH servers to accept FIDO/U2F security key signatures that were generated without the required physical user touch. The Verify() method for sk-ecdsa-sha2-nistp256@openssh.com and sk-ssh-ed25519@openssh.com key types failed to check the User Presence flag, enabling unattended use of stolen or relayed hardware-token signatures. No public exploit identified at time of analysis and EPSS is very low (0.01%), but SSVC rates technical impact as total with automatable exploitation.
Constraint extension stripping in the golang.org/x/crypto SSH agent client (versions prior to 0.52.0) allows remote SSH hosts to use forwarded keys without the destination restrictions the user intended. When clients added keys to a remote agent, extensions such as restrict-destination-v00@openssh.com were silently dropped during serialization, effectively converting scoped keys into unrestricted ones on downstream hosts. No public exploit identified at time of analysis and EPSS is very low (0.02%), but SSVC rates technical impact as total and automatable.
Denial-of-service via unchecked memory allocation in russh (Rust SSH library) versions <= 0.60.2 allows local SSH agent peers to trigger uncontrolled buffer growth by sending oversized frame length values, and in pre-0.58.0 releases the same CryptoVec allocation path was reachable from remote SSH transport and zlib decompression buffers. The flaw stems from CryptoVec performing unchecked capacity growth, unchecked length arithmetic, and unsafe allocation/locking calls including NonNull::new_unchecked on potentially failed allocations, which can abort the process under memory pressure. Publicly available exploit code exists in the form of researcher-supplied PoC tests demonstrating both rejection on patched code and crash behavior on historical versions; no public exploit identified at time of analysis for active campaigns and the issue is not listed in CISA KEV.
Remote code execution in Kopia backup server (≤ 0.22.3) allows unauthenticated attackers to run arbitrary OS commands as the Kopia process user via a single HTTP request to /api/v1/repo/exists when the server is launched with --without-password. Publicly available exploit code exists through the published GHSA advisory and PR diff; no public exploit identified at time of analysis as being weaponized in the wild, but the trivially exploitable vector (CVSS 9.8) and detailed write-up make weaponization straightforward. The bug stems from naive space-splitting of attacker-controlled sshArguments that is fed to exec.CommandContext("ssh"), letting an -oProxyCommand= token trigger $SHELL -c execution before any SSH transport is established.
Path traversal in Pipecat's development runner allows unauthenticated remote attackers to read arbitrary files when the --folder flag is used. The /files/{filename:path} endpoint fails to validate paths containing %2F-encoded directory separators, bypassing Starlette's URL normalization. Fixed in version 1.2.0 with no public exploit identified at time of analysis.
Argument/command injection in OpenSSH before 10.3 lets shell metacharacters embedded in an untrusted username trigger command execution on the SSH-client host. It affects deployments that both feed an attacker-influenced username to the ssh command line and use a non-default ssh_config where %-token expansion (e.g. in ProxyCommand/LocalCommand) is enabled. There is no public exploit identified at time of analysis, EPSS is negligible (0.01%), and it is not in CISA KEV; a fixed release (10.3/10.3p1) is available.
OpenSSH before version 10.3 mishandles the authorized_keys principals option when a principals list is combined with a Certificate Authority that uses certain comma character patterns, allowing authenticated local or remote users to disclose sensitive authorization information or manipulate authentication decisions. This vulnerability affects all OpenSSH versions prior to 10.3p1 and requires authenticated access (PR:L) with non-trivial attack complexity (AC:H), resulting in partial confidentiality and integrity impact. No public exploit code or active exploitation has been identified at time of analysis.
Privilege-escalation exposure in OpenSSH before 10.3 (fixed in 10.3p1) where scp, when run by root using the legacy SCP protocol flag -O and without -p (preserve mode), may write a downloaded file with setuid or setgid bits set, contrary to user expectation. A malicious or compromised SSH server (or a man-in-the-middle on the transfer) could thereby cause an attacker-controlled binary to land on disk as a setuid/setgid-root executable, enabling local privilege escalation when it is later run. There is no public exploit identified at time of analysis, EPSS is very low (0.04%), and CISA SSVC rates exploitation as 'none' though technical impact as 'total'.
SSRF in Soft Serve Git server versions 0.6.0 to 0.11.3 allows authenticated attackers to make requests to internal services. PoC and patch available.
Gogs is an open source self-hosted Git service. [CVSS 8.8 HIGH]
Hardcoded OS credentials in Glory RBG-100 cash recycler systems using ISPK-08 software component. Physical cash handling equipment ships with known default credentials enabling complete system takeover.
SiYuan knowledge management system prior to 3.5.5 has a path traversal in /api/file/copyFile allowing arbitrary file operations on the server.
The Terraform/OpenTofu Proxmox Provider prior to version 0.93.1 contains a path traversal vulnerability in its SSH sudoer configuration documentation that permits attackers to escape directory restrictions using ../ sequences and modify arbitrary files on the system. Public exploit code exists for this vulnerability, affecting users who implement the documented SSH configuration. The vulnerability has been patched in version 0.93.1 and a fix is available.
OpenClaw AI assistant versions prior to 2026.1.29 contain two command injection vulnerabilities: unescaped user input in SSH project paths allows remote code execution on SSH hosts, and insufficient validation of SSH target parameters enables local command execution through malicious flag injection. An attacker can exploit these flaws to achieve arbitrary code execution either remotely via SSH or locally on the system running OpenClaw.
n8n is an open source workflow automation platform. [CVSS 8.1 HIGH]
Ziroom ZHOME A0101 devices running version 1.0.1.0 use hardcoded default credentials in the Dropbear SSH service, enabling unauthenticated remote attackers to gain unauthorized access with high impact to confidentiality, integrity, and availability. Public exploit code exists for this vulnerability, and the vendor has not provided a patch or response. While exploitation requires specific conditions, security professionals should prioritize assessment and credential rotation for affected systems.
Soft Serve self-hosted Git server versions 0.11.2 and below have a critical authentication bypass that allows unauthenticated access to private repositories.
Operation And Maintenance Security Management System versions up to 3.0.12. is affected by command injection (CVSS 8.8).
Stored XSS in Termix File Manager (versions 1.7.0-1.9.0) allows attackers with SSH server access to execute arbitrary JavaScript by uploading malicious SVG files that bypass content sanitization. When a Termix user previews the crafted file, the payload executes within the application context with full access to sensitive operations. Public exploit code exists and no patch is currently available.
GNU Bash through 4.3 bash43-026 does not properly parse function definitions in the values of environment variables, which allows remote attackers to execute arbitrary commands via a crafted. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
freeSSHd.exe in freeSSHd through 1.2.6 allows remote attackers to bypass authentication via a crafted session, as demonstrated by an OpenSSH client with modified versions of ssh.c and sshconnect2.c. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 75.9%.
The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX and Linux, when old-style password. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 25.7%.
Memory exhaustion in OpenSSH's transport-layer decompression path allows an authenticated remote user to grow the memory footprint of the per-connection process by sending a compressed payload that inflates beyond the maximum supported packet size (CVE-2026-110927, CVSS 4.3). The flaw is only reachable when SSH compression has been negotiated on the connection, and per the CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) a valid, authenticated session is required, matching OpenSSH's default delayed-compression behaviour in which zlib activates only after authentication. Impact is confined to availability - memory growth in the handling process with no code execution, integrity, or confidentiality effect - and no public exploit code has been identified at time of analysis and the issue is not in CISA KEV; affected scope per available vendor data is Red Hat Enterprise Linux 6 through 10, OpenShift Container Platform 4, and Red Hat Hardened Images.
OpenSSH deployments with GSSAPI authentication and credential delegation enabled can retain delegated credentials after a failed GSSAPI attempt, potentially allowing a subsequent successful login on the same connection to inherit unauthorized credential state. This flaw (CWE-459) is rated CVSS 4.8 and affects Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. No public exploit identified at time of analysis, and exploitation requires non-default GSSAPI configuration plus a specific sequence of failed then successful login, limiting real-world risk.
An authenticated peer on an OpenSSH connection can recover plaintext belonging to another channel when SSH compression is negotiated, because all channels multiplexed over one connection share a single LZ77 dictionary and chosen-plaintext length analysis exposes the content of a victim channel's traffic. Affected deployments include OpenSSH as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. Severity is medium (CVSS 5.3, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N); exploitation requires authentication and is limited by high attack complexity, the non-default nature of compression in many hardened configurations, and the need for genuinely co-resident attacker and victim channels, and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Command injection in the OpenSSH client allows shell metacharacters placed in a command-line username - specifically '$' or a non-trailing backslash - to reach a shell when the ssh configuration expands the %u token inside a ProxyCommand or Match exec directive, giving arbitrary command execution with the privileges of the account that runs ssh. Reachability is conditional: a default OpenSSH configuration is not affected, and the attack requires a non-default config using %u in those directives plus a username that an attacker can control or influence through a script, wrapper, or application that forwards untrusted input as the username, with a user or process actually initiating the connection (UI:R). Affected builds are OpenSSH as shipped in Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; no public exploit identified at time of analysis. Note the scoring divergence: Red Hat assigns 5.4 (C:L/I:L/A:N), while our independent assessment is higher at CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H because command execution under the invoking account can fully compromise confidentiality, integrity, and availability of that account's data and sessions.
Path traversal in the OpenSSH sftp client enables a malicious or compromised SFTP server to cause files downloaded during an sftp copy to be written outside the local directory the user selected. The flaw is client-side and requires user interaction to initiate the transfer from an untrusted server; it is rated CVSS 6.5 with high integrity impact but no confidentiality or availability impact. No public exploit code or confirmed active exploitation was identified at time of analysis, and Red Hat has published tracking for Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4.
Source-IP misattribution in fail2ban's default sshd filter allows a remote, unauthenticated attacker to have fail2ban ban an arbitrary IP address of their choosing. Because OpenSSH records the offered username verbatim in its log lines and fail2ban 0.10.5 through 1.1.1 (before commit ddd879d22664904ace24e1255ac6571808c58187) accepts an "on <token>" suffix after the parsed host address, an attacker can connect to the SSH service using a username such as "x VICTIM-IP on" and cause subsequent failed-login entries to be attributed to that victim address, resulting in a temporary firewall block against a legitimate user or host. The impact is availability-only (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, base 5.3 Medium) with no confidentiality or integrity loss; no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
This is a genuinely low-priority issue by every available signal, not a high-CVSS alarm. Local privilege retention in OpenSSH sshd-session on obsolete platforms (QNX 6, SCO OpenServer 5) allows an authenticated user to cause sshd-session to run with root privileges when GatewayPorts or StreamLocalForwarding is enabled and the host lacks support for file-descriptor passing and unprivileged PTY allocation. Exploitation is confined to those specific configurations, no public exploit has been identified at time of analysis, and the assessed CVSS is 2.9.
OpenSSH sshd builds compiled against the macOS 27 (or later) SDK silently lose their sandbox, removing a containment layer that normally limits the damage an attacker can do if they manage to compromise or corrupt the sshd process. Only OpenSSH through 10.6 built against that specific SDK is affected, which is far from the default configuration for Linux, BSD, or older-macOS deployments. This is a low-severity defense-in-depth regression rather than a directly exploitable flaw - the sandbox loss causes no impact on its own and only produces harm when chained with a separate exploitable sshd vulnerability that the sandbox would otherwise have contained; no public exploit was identified at time of analysis, and the CVSS 3.1 score (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N) reflects that chaining requirement and high attack complexity.
Misinterpretation of the literal configuration value "none" in sshd in OpenSSH before 10.6 causes the daemon to treat the keyword as a filename instead of as a feature-disable value, yielding limited integrity and availability impact with no confidentiality loss. Per our independent assessment this is a low-severity, low-priority issue despite being in ubiquitous software: exploitation is local only (AV:L), requires high attack complexity (AC:H) and high privileges (PR:H), and depends entirely on an administrator having set an sshd option to the literal string "none" in a non-default configuration, so there is no remote or default-configuration exposure. Exploitation status: no public exploit identified at time of analysis, and the issue is not listed in CISA KEV; the only reference is the upstream OpenSSH 10.6 release notes.
OpenSSH servers prior to 10.6 fail to enforce the 'restrict' keyword in authorized_keys against tunnel (tun/tap) forwarding, letting a user who already holds a restricted key open a forwarding tunnel that the administrator explicitly intended to block. This is a control-bypass rather than an access-control failure: the attacker must already possess a valid SSH key provisioned with 'restrict' (assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N), and the flaw only matters on servers older than 10.6 where tunnel forwarding was the specific capability the keyword was relied on to deny. Impact is limited to integrity (establishing the forwarding channel) with no confidentiality or availability loss, the base score is 2.5, and no public exploit code or CISA KEV activity is identified at time of analysis.
Availability degradation in OpenSSH before 10.6 occurs because sshd and ssh fail to enforce the maximum packet length while decompressing highly compressed SSH data, allowing a peer on a connection with negotiated SSH compression to trigger excessive resource consumption. Exploitation requires compression (zlib or zlib@openssh.com) to be negotiated-often not the case on modern OpenSSH servers where compression is disabled or delayed until after authentication-and an active malicious or compromised SSH peer; the independent assessment scores this as remote, network-reachable, unauthenticated with low availability impact and no confidentiality or integrity impact. No public exploit identified at time of analysis.
ssh-keygen in OpenSSH versions before 10.6 can assign incorrect expiration timestamps to generated certificates when a Daylight Saving Time transition is mishandled, producing a bounded integrity error in the certificate's validity window. The issue is local: it requires a user to run ssh-keygen for certificate creation or signing, and it only manifests around DST changes, with slightly more pronounced effects noted for certain Antarctic time zones. With a CVSS score of 2.5 and no public exploit identified at time of analysis, this is a low-priority correctness bug rather than a remotely exploitable security flaw.
The sshd and ssh components of OpenSSH before 10.6 can be made to negotiate and use the LZ77 dictionary-coder compression scheme, a behavior the 'Crossing the Streams' research (arXiv 2609.07709) identifies as contraindicated because compression-derived information leakage can be measured from an observed session. A remote, unauthenticated attacker who can observe and influence the target connection and repeatedly sample it may recover a limited amount of confidential data, but only where the vulnerable compression mode is actually in use; integrity and availability are unaffected. This is a low-severity, low-priority issue (CVSS 3.1 base 3.7; AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) despite being network-reachable and unauthenticated, because exploitation demands an active compression configuration, a privileged observation vantage point, and sustained measurement - no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Directory traversal in the OpenSSH sftp client before 10.6 can cause files to be written to unintended locations when a user performs a recursive copy operation against an attacker-controlled or compromised SFTP server. Exploitation requires the victim to initiate a recursive transfer such as get -r or put -r, and the malicious server supplies crafted path/filename entries containing traversal components; this is a client-side trust issue, not a flaw in an exposed sshd service. No public exploit identified at time of analysis, and the assessed CVSS 3.1 score is 4.2 with high attack complexity and user interaction required.
Unbounded key-derivation cost parameters in Bouncy Castle for Java before 1.86 allow a denial of service against applications that parse attacker-influenced cryptographic structures: PBKDF2 iteration counts, derived-key lengths, scrypt parallelization factor p, and OpenSSH v1 bcrypt round counts were read straight from untrusted input and used to drive the KDF before any password or MAC verification could reject the data. Affected code paths include the RFC 9579 PBMAC1 MAC calculator builders (JcePBMac1CalculatorBuilder, PKCS12PBEUtils.createPBMac1Calculator reached via PKCS12PfxPdu.isMacValid), the PKCS#8/PKCS#12 scrypt cost guards, the raw JCA PBKDF2 provider, and OpenSSH v1 private-key parsing in Bouncy Castle for Java, LTS (before 2.73.13) and FIPS (bcpkix-fips before 1.0.13 / 2.0.13 / 2.1.13). Impact is availability-only (CVSS:4.0 5.3; assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L): exploitation requires the victim application to passively process a malicious blob and is unauthenticated (PR:N), but no key material or data is exposed, and there is no public exploit identified at time of analysis.
Memory exhaustion in the sshd-sftp component of Apache MINA SSHD (1.0.0 through 2.19.0 and 3.0.0-M1 through 3.0.0-M5) lets an authenticated remote SFTP client crash the server by driving the SFTP v6 check-file-name/check-file-handle extension to build an oversized reply entirely in server memory. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), the session must be authenticated and must negotiate SFTP protocol version 6, and the attacker must point the request at a very large (possibly sparse) file using a tiny block size such as the 256-byte minimum, so that file-size divided by block size yields an enormous number of hashes; availability impact is high while confidentiality and integrity are unaffected. This is a genuine but bounded availability risk with no public exploit identified at time of analysis, and deployments that already cap SFTP message size (typically 256kB, as OpenSSH does) are not exposed.
OpenSSH sshd before version 10.5 fails to enforce the `restrict` keyword in `authorized_keys` against tunnel forwarding, allowing a constrained SSH key holder to establish tun-device tunnels that the administrator explicitly intended to block. The flaw affects all OpenSSH releases prior to 10.5 and is classified as a policy-enforcement bypass with low integrity impact. No active exploitation is confirmed per SSVC (exploitation: none) and the vulnerability is absent from the CISA KEV catalog, placing this firmly in the low-urgency tier despite OpenSSH's near-ubiquitous deployment footprint.
Use-after-free (CWE-416) in OpenSSH's ssh client component affects all releases before version 10.5, triggered when a specific pair of remote-forwarding operations occur concurrently, causing access to freed realloc'd memory. A malicious or compromised SSH server could exploit this race condition against a connecting client to achieve partial information disclosure or limited memory corruption. No public exploit has been identified and CISA SSVC rates exploitation as none with partial technical impact, consistent with the moderate CVSS score of 4.8.
OpenSSH ssh-agent before version 10.5 permits remote execution of agent operations - including adding authentication tokens and using SSH keys - that were architecturally intended to be restricted to local access only. The trust boundary failure stems from a misinteraction between the agent locking mechanism and the session-bind@openssh.com extension, allowing an authenticated remote actor to cross the local/remote privilege boundary. No public exploit has been identified at time of analysis, and SSVC assessment confirms no current exploitation activity; however, the network-accessible vector and ubiquitous deployment footprint of OpenSSH make patching to 10.5 the appropriate response for any environment using agent forwarding.
OpenSSH sshd before version 10.4 fails to consistently enforce its built-in minimum authentication delay, undermining the rate-limiting defense designed to slow credential-guessing attacks against SSH services. All OpenSSH releases prior to 10.4 are affected across all platforms, enabling unauthenticated remote attackers to submit authentication attempts at a rate higher than the daemon intends to permit. No public exploit code has been identified and the vulnerability is absent from CISA KEV; however, the trivial attack complexity combined with OpenSSH's near-universal deployment footprint makes prompt patching appropriate.
OpenSSH sshd before version 10.4 silently ignores the GSSAPIStrictAcceptorCheck configuration directive when the server is integrated with Windows Active Directory, defeating a security control that administrators rely on to enforce GSSAPI acceptor name validation during Kerberos-based SSH authentication. This undocumented behavior means AD-joined SSH servers may accept GSSAPI authentications against unintended Kerberos service principals regardless of how the option is configured, yielding limited confidentiality and integrity impact. No public exploits or active exploitation have been identified; the CVSS AC:H rating reflects the specific environmental prerequisites required for exploitation.
OpenSSH's internal-sftp subsystem silently discards all command-line arguments beyond position 9, allowing authenticated SFTP users to bypass security restrictions that administrators intended to enforce via those later-positioned arguments. All OpenSSH releases before 10.4 are affected when sshd_config supplies more than nine arguments to the internal-sftp subsystem, which is a non-default but legitimate administrative pattern used for directory restriction, read-only enforcement, and umask control. No public exploit has been identified and this vulnerability is not listed in the CISA KEV catalog; however, sites relying on complex internal-sftp argument chains for access policy enforcement face a direct, silent policy bypass.
Path traversal in the scp utility of OpenSSH before 10.4 causes files to be written into the parent directory of the intended destination during remote-to-remote copy operations. The root cause is CWE-23 (Relative Path Traversal): scp fails to canonicalize or sanitize paths when relaying data between two remote hosts, allowing an attacker controlling a malicious endpoint to influence where transferred files land. No public exploit identified at time of analysis, and active exploitation has not been confirmed by CISA KEV; the CVSS AC:H and UI:R metrics significantly constrain real-world exploitability.
Path traversal in the OpenSSH sftp client before version 10.4p1 allows an attacker-controlled server to write downloaded files outside the user's intended target directory when the 'sftp server:/path .' bulk-download syntax is used. Affected are all OpenSSH deployments where users sftp from untrusted or attacker-controlled hosts, which in practice spans virtually every Linux and Unix environment. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, though the ubiquity of OpenSSH elevates aggregate exposure despite the moderate per-instance severity.
OpenSSH's GSSAPI authentication cleanup routine contains a heap out-of-bounds read (CWE-125) triggered when the auth-indicators array lacks a trailing NULL terminator, allowing a remote unauthenticated attacker to crash the SSH authentication path and deny SSH service availability. Exploitation is constrained by high attack complexity (AC:H) due to the non-default Kerberos/GSSAPI configuration requirement, limiting real-world exposure to a minority of deployments. No active exploitation is confirmed (not in CISA KEV), no public exploit code has been identified, and the impact is restricted to partial availability loss with no confidentiality or integrity consequence.
X11 forwarding session hijacking in OpenSSH enables a local unprivileged attacker sharing a Linux client host to intercept and partially manipulate the victim's forwarded X11 display traffic by squatting on the predictable abstract UNIX domain socket name before the SSH client creates it. Affected deployments span OpenSSH packages across Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and OpenShift Container Platform 4. No public exploit code has been identified at time of analysis, but successful exploitation yields high-confidence access to sensitive X11 session data including keystrokes, window contents, and clipboard material.
Client-side Denial of Service in OpenSSH's Diffie-Hellman Group Exchange implementation allows a malicious SSH server to crash connecting clients running in FIPS mode. When a victim initiates an SSH connection to an attacker-controlled server, the server sends crafted DH-GEX group parameters that trigger a double free (CWE-415) during FIPS known-group validation, terminating the client process. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, the constraint that only FIPS-mode clients are affected limits real-world impact to regulated or government environments.
Resource exhaustion in Russh's SSH server identification-string reader allows unauthenticated remote attackers to hold connection setup resources indefinitely during the cleartext pre-authentication phase. Russh versions 0.34.0-beta.1 through 0.60.x used the same permissive identification reader for both client and server roles, failing to cap the number of pre-banner lines a connecting client could send before the SSH identification string - a constraint OpenSSH enforces strictly per RFC 4253. Any application serving SSH via russh is exposed to this pre-auth resource-holding condition. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
OpenSSH before 10.3 fails to confirm connection multiplexing in proxy-mode sessions, allowing local attackers with user interaction to bypass intended access controls and potentially manipulate multiplexed connections. The vulnerability affects OpenSSH versions prior to 10.3p1 and requires local access with user interaction (UI:R) on the affected system; while the CVSS score is low (2.5) and integrity impact is limited, the omission of confirmation mechanisms in proxy-mode multiplexing creates a logic flaw that could enable unauthorized session hijacking or redirection in multi-user environments.
OpenSSH before 10.3 incorrectly interprets ECDSA algorithm specifications in PubkeyAcceptedAlgorithms and HostbasedAcceptedAlgorithms configuration options, allowing authenticated users to authenticate using unintended ECDSA variants. The vulnerability requires authenticated network access and high attack complexity, resulting in a low CVSS score of 3.1 with integrity impact but no confidentiality or availability loss. No public exploit code or active exploitation has been documented.
SCP client implementations across Red Hat Enterprise Linux 6-10 and OpenShift Container Platform 4 are vulnerable to path traversal during file transfer, allowing a malicious SCP server to write files outside the designated working directory and potentially execute arbitrary code or modify system configuration. This vulnerability mirrors CVE-2019-6111 in OpenSSH; unauthenticated remote attackers can exploit it with high user interaction (the victim must initiate an SCP connection to a malicious server), resulting in confidentiality, integrity, and availability compromise. No public exploit code or active exploitation has been confirmed at the time of analysis.
A remote code execution vulnerability (CVSS 6.9) that allows denial of service. Remediation should follow standard vulnerability management procedures. Vendor patch is available.
Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself.
A low‑privileged local attacker who gains access to the UBR service account (e.g., via SSH) can escalate privileges to obtain full system access. This is due to the service account being permitted to execute certain binaries (e.g., tcpdump and ip) with sudo. [CVSS 7.8 HIGH]
Outdated MAC algorithms in SSH implementations for Mrs1000 and Lms1000 device firmware enable network-positioned attackers to tamper with session data integrity without user interaction. An attacker with network access can manipulate transmitted SSH traffic due to the use of cryptographically weak message authentication codes. No patch is currently available for affected devices.
Weak CBC cipher suite implementations in SSH services across SSH, LMS1000, and MRS1000 devices enable network-positioned attackers to observe or modify encrypted SSH traffic without authentication. The vulnerability requires user interaction and network access but poses a confidentiality risk to sensitive communications. No patch is currently available.
Weblate versions up to 5.16.0 contains a vulnerability that allows attackers to an argument injection to `ssh-add` (CVSS 6.6).
There is a misconfiguration vulnerability inside the Infotainment ECU manufactured by BOSCH. The vulnerability happens during the startup phase of a specific systemd service, and as a result, the following developer features will be activated: the disabled firewall and the launched SSH server. [CVSS 6.8 MEDIUM]
A flaw was found in Dropbear. When running in multi-user mode and authenticating users, the dropbear ssh server does the socket forwardings requested by the remote client as root, only switching to the logged-in user upon spawning a shell or performing some operations like reading the user's files. [CVSS 5.4 MEDIUM]
ZOC Terminal 7.25.5 contains a denial of service vulnerability in the private key file input field that allows attackers to crash the application. [CVSS 7.5 HIGH]
With physical access to the device and enough time an attacker can desolder the flash memory, modify it and then reinstall it because of missing encryption.
with the restriction that the password is only randomized if the configured date versions up to 2022. contains a security vulnerability.
Gitlab versions up to 18.6.4 is affected by allocation of resources without limits or throttling (CVSS 5.3).
Command injection in the NetBird desktop client (versions 0.60.0 through 0.74.6) lets a malicious or compromised peer inject arbitrary OpenSSH directives - including command-executing ones - into the system-wide drop-in config of other clients' Linux, macOS, Windows and FreeBSD hosts. Exploitation requires the attacker to control an enrolled peer whose crafted FQDN or hostname containing a double quote is distributed to the victim, and the injected command runs only when a local user subsequently invokes ssh, so peer membership plus a local user action are both prerequisites rather than an unauthenticated internet-facing attack. NetBird 0.74.7 fixes the issue by rejecting peer names that are not valid DNS names; no public exploit identified at time of analysis, and the Android and iOS apps are not affected.
Remote code execution in OpenSSH for Windows (the Microsoft OpenSSH server component) can be triggered over the network by an unauthenticated attacker with no user interaction, according to the CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N and a 9.8 base score. The flaw is a use-after-free that can lead to memory corruption and potential code execution or denial of service, but exposure is limited to Windows hosts where the optional OpenSSH Server feature is installed and listening, typically on TCP/22. No public exploit identified at time of analysis, and confidence is limited by single-source reporting; defenders should treat any network-exposed Windows sshd listener as high risk and restrict or firewall the SSH port pending patching.
Local privilege escalation in OpenSSH for Windows allows an authenticated attacker to elevate privileges by triggering a double-free memory corruption. Affected builds include Windows 10, Windows 11, and Windows Server versions prior to the fixed builds listed in Microsoft's advisory. No public exploit identified at time of analysis; a vendor-released patch is available.
Heap-based buffer overflow in OpenSSH for Windows can let an unauthenticated network attacker execute code, but the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H and the independent assessment indicate the victim must initiate the vulnerable SSH operation, likely by using an affected Windows OpenSSH client against an attacker-controlled or compromised SSH server. Affected builds span Windows 10, Windows 11, and Windows Server 2019, 2022, and 2025 as enumerated in EUVD-2026-99587; Microsoft has released patched builds through the MSRC update guide. No public exploit identified at time of analysis, and CISA SSVC marks exploitation as none and Automatable as no, so risk is gated by user interaction and the need for the victim to connect to attacker-influenced infrastructure.
Relative path traversal in OpenSSH for Windows (CWE-23) can allow an unauthenticated remote attacker to escape intended directories during an SSH interaction and, ultimately, execute code on the affected host - carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and rated by SSVC as having total technical impact. Exploitation is not attacker-autonomous: it requires the victim to use the OpenSSH for Windows component and to initiate or accept an SSH connection to an attacker-controlled or compromised endpoint (the UI:R user-interaction requirement), and the host must be running a build below its fixed release (for example Windows 11 24H2 below 10.0.26100.9711 or Windows Server 2022 below 10.0.20348.5761). Current intelligence shows no public exploit identified at time of analysis, SSVC exploitation status of 'none', and non-automatable delivery, so this is a high-priority-on-paper issue whose real-world urgency is tempered by the lack of confirmed exploitation - vendor patches are available per the Microsoft advisory and should still be prioritized.
A heap-based buffer overflow in the OpenSSH for Windows component allows an authenticated local attacker with a low-privileged account to elevate privileges on the affected host, with high attack complexity required to reliably shape the heap for exploitation. Affected systems are Windows 10, Windows 11 and Windows Server 2019/2022/2025 installations whose OpenSSH component predates Microsoft's patched builds (for example, Windows 11 24H2/25H2 <10.0.26100.9711 and <10.0.26200.9711, Windows Server 2025 <10.0.26100.33650); updated builds are not exploitable. No public exploit code has been identified at time of analysis and Microsoft has released fixes, but the 7.0 CVSS score reflects full confidentiality, integrity and availability impact if the overflow is successfully turned into code execution; this is a genuine but second-tier local privilege-escalation issue rather than a remotely wormable flaw, and there is no confirmed active exploitation (no CISA KEV listing).
Local privilege escalation in OpenSSH for Windows stems from a use-after-free (CWE-416) in the SSH component shipped with supported Windows builds, allowing an authenticated low-privileged user who already holds a foothold on the host to corrupt memory inside the OpenSSH process and elevate to the privileges of that process, with high impact across confidentiality, integrity and availability (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is strictly local: there is no remote or network vector, no user interaction is required, and exploitation presupposes a valid low-privilege account plus the vulnerable OpenSSH for Windows component being installed and in use on an unpatched build. No public exploit code has been identified at the time of analysis, CISA's SSVC decision framework records exploitation as none and the flaw as not automatable, and Microsoft has released vendor patches for all affected Windows versions.
Heap-based buffer overflow in OpenSSH for Windows - the optional OpenSSH client/server component shipped with Windows 10, Windows 11, and Windows Server 2019/2022/2025 - can allow code execution in the context of the vulnerable process, with the CVSS v3.1 vector AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H (reported score 7.5) reflecting full confidentiality, integrity and availability impact. Exploitation is unauthenticated (PR:N) but is gated by two concrete limiters: User Interaction is Required (UI:R), implying a victim must actively initiate or accept the vulnerable SSH operation rather than being hit passively, and Attack Complexity is High (AC:H), meaning the attacker must satisfy a non-trivial precondition such as a specific heap or memory layout. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA SSVC Exploitation: none; KEV: no), and CISA's SSVC also rates the flaw as not automatable, although technical impact is assessed as total - on balance the signals point to a serious-but-not-emergency priority for hosts running the OpenSSH feature.
Denial of service in the OpenSSH server component (sshd) shipped as an optional feature of Windows allows an unauthenticated, remote attacker who can reach the SSH port to consume host resources without throttling, degrading or exhausting the service so legitimate SSH sessions can no longer be established. Only Windows builds that actually have the OpenSSH Server capability installed, enabled and network-reachable are at risk - the feature is not on by default for most client installs, which materially narrows the attack surface, and the impact is availability-only (C:N/I:N/A:H). The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5), CISA's SSVC assessment records exploitation as none, automatable as yes and technical impact as partial, and there is no public exploit identified at time of analysis; a vendor fix is available.
Command injection in the OpenSSH ssh client before version 10.6 occurs when a username supplied on the command line contains a '$' or '\' character, which is not correctly escaped or quoted and can be interpreted as shell syntax. The flaw is assessed as CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and requires the victim to invoke ssh with an attacker-controlled username - for example from a crafted ssh:// URI, a shared connection string, or a script or alias - so it is not remotely triggerable against a default server. No public exploit was identified at time of analysis, EPSS is 0.13% (2nd percentile), and the issue does not appear on CISA KEV; this is a genuine but not emergency-grade issue, and patched clients (10.6 and later) are unaffected.
OpenSSH sshd before 10.6 can incorrectly persist GSSAPIAuthentication state across authentication attempts when GSSAPIAuthentication is enabled, allowing a remote, unauthenticated attacker to influence authentication integrity on the same connection. This is a non-default configuration issue: stock OpenSSH deployments without Kerberos/GSSAPI are not affected, and the attacker must drive a sequence of authentication attempts (high attack complexity). No public exploit code has been identified, EPSS is very low (0.08%, 0th percentile), and CISA SSVC reports no exploitation; the vendor has released a fix in OpenSSH 10.6.
Credentials can incorrectly persist after a failed GSSAPIAuthentication attempt in the sshd daemon of OpenSSH before 10.6, allowing an authentication context that should have been discarded to remain usable and potentially granting access under another identity (CWE-669, integrity impact). Only hosts that explicitly enable GSSAPIAuthentication are affected, since the OpenSSH default is 'no', so exposure is largely limited to Kerberos/GSSAPI-integrated environments; the flaw is fixed in OpenSSH 10.6. No public exploit code has been identified at time of analysis, EPSS is negligible (0.08%), and CISA SSVC records no observed exploitation and rates the issue as non-automatable with partial technical impact, so real-world risk is moderate despite the 7.5 'High' base score.
A partial authentication bypass in Apache MINA SSHD lets a remote attacker satisfy a repeated-public-key multi-authentication policy by presenting the same public key twice, so a server configured to demand two distinct keys can be entered with only one of them. Affected are versions before 2.20.0 and 3.0.0-M1 through 3.0.0-M5 of the sshd-core component; the vendor assigns CVSS 3.1 8.1 (High, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), where PR:L reflects that the attacker must already legitimately possess at least one accepted key pair. Exploitation is confined to the non-default hardened configuration that requires repeated/multiple public keys (the equivalent of OpenSSH's AuthenticationMethods "publickey,publickey"); single-key or password-based deployments are not affected, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Use-after-free in Microsoft's OpenSSH for Windows enables unauthenticated network attackers to achieve remote code execution across a broad range of Windows 10, Windows 11, and Windows Server releases. The CVSS vector (AV:N/AC:H/PR:N/UI:R) indicates exploitation is constrained by high attack complexity and a requirement for user interaction, consistent with a client-side attack path where a victim must connect to an attacker-controlled SSH endpoint. Microsoft has released patched builds across all affected Windows versions; no public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in SSH.NET's ScpClient.Download() enables a malicious, compromised, or man-in-the-middle SCP server to write arbitrary files anywhere the client process has write access during recursive directory downloads. All SSH.NET NuGet package versions up to and including 2025.1.0 are affected; the vulnerability is analogous to CVE-2019-6111 in OpenSSH but extends to directory traversal. No public exploit code or CISA KEV listing has been identified at time of analysis, though the integrity impact is high given the file-write primitive can overwrite SSH authorized keys, shell rc files, or application binaries.
Path traversal in rclone's `serve restic` REST API allows any attacker with network access to the endpoint to read, create, overwrite, or delete objects outside the operator-configured backend directory. The flaw spans rclone v1.40 through v1.74.4 and affects WebDAV, FTP, SFTP, HTTP, and Memory backends - but not S3-compatible or local filesystem backends, which encode `..` as literal filename characters. A fully functional, step-by-step proof of concept has been publicly released; no CISA KEV listing exists at time of analysis.
Command-restriction bypass in Apache MINA SSHD (server-side) lets a user who authenticates with an OpenSSH user certificate carrying a force-command directive execute arbitrary commands instead of the single restricted command the certificate authority intended. The server accepts and honors such certificates but silently ignores the force-command and verify-required options, breaking the security model that certificate issuers rely on to constrain principals. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw is confirmed and fixed by the Apache Software Foundation in versions 2.19.0 and 3.0.0-M5.
Argument injection in bosh-cli versions before v7.10.4 lets a compromised or malicious BOSH Director inject arbitrary OpenSSH command-line options into the ssh process that the CLI spawns locally, achieving code execution on the operator's own workstation. It triggers during non-interactive SSH paths such as bosh ssh -c, bosh logs -f, and similar flows where the CLI builds an ssh command from Director-supplied data. No public exploit is identified at time of analysis, and it is not listed in CISA KEV; the CVSS 4.0 base score is 7.7 (High).
Memory corruption in the OpenSSH client (ssh) before 10.4 lets a malicious or compromised SSH server trigger a use-after-free on the connecting client by changing its host key during a key re-exchange (rekey), potentially leading to information disclosure or code execution in the client process. Only the client side is affected; the server is not vulnerable. There is no public exploit identified at time of analysis and it is not on CISA KEV, and EPSS is low (0.25%, 16th percentile), but the flaw is fixed in OpenSSH 10.4/10.4p1.
Denial of service in OpenSSH sshd before 10.4 lets remote unauthenticated attackers exhaust server resources by driving excessive authentication attempts, because the MaxAuthTries cap was not correctly enforced for the GSSAPIAuthentication path. Only deployments that have enabled GSSAPI-based authentication are exposed, and there is no public exploit identified at time of analysis. EPSS is low (0.34%, 26th percentile) and CISA SSVC records no observed exploitation, so this is a real but non-urgent availability issue rather than a code-execution threat.
Security-control bypass in OpenSSH sshd before 10.4 causes the DisableForwarding=yes hardening directive to be silently ignored when PermitTunnel=yes is also set, so tun-device forwarding remains available despite an administrator's explicit policy to disable all forwarding. Affected operators are those who rely on DisableForwarding as a defense-in-depth restriction; the flaw lets an authenticated user establish layer-2/3 tunnels the configuration was meant to forbid. There is no public exploit identified at time of analysis, EPSS is low (0.13%, 3rd percentile), and it is not on CISA KEV.
Remote denial-of-service in russh, a Rust implementation of the SSH protocol, allows unauthenticated remote attackers to exhaust server memory by sending small compressed SSH packets that inflate to massive sizes post-decompression. Affecting all versions from 0.34.0 through 0.61.0, the flaw stems from missing post-decompression size enforcement in Decompress::decompress(), allowing payloads under the 256 KiB wire cap to expand beyond 128 MiB. No public exploit identified at time of analysis, but the advisory includes a detailed PoC demonstrating pre-authentication exploitation against default server configurations.
SSH public-key authentication bypass in AsyncSSH 2.22.0 (Python pip package) allows remote attackers to log in as another identity when the server uses the OpenSSH-style per-user pattern 'AuthorizedKeysFile authorized_keys/%u'. Because the %u token is expanded from the raw SSH username without rejecting '/', '\', or '..', an attacker supplying a traversal username (e.g. '../../../attacker.pub') forces the server to read an authorized-keys file outside the intended directory; if that file contains the attacker's public key, authentication succeeds. Publicly available proof-of-concept exploit code exists (harness plus exploit script in the advisory), but there is no public exploit identified as being used in the wild and the issue is not in CISA KEV; EPSS is low at 0.22%.
Authentication bypass in the Go x/crypto/ssh library (versions before 0.52.0) allows SSH servers to accept FIDO/U2F security key signatures that were generated without the required physical user touch. The Verify() method for sk-ecdsa-sha2-nistp256@openssh.com and sk-ssh-ed25519@openssh.com key types failed to check the User Presence flag, enabling unattended use of stolen or relayed hardware-token signatures. No public exploit identified at time of analysis and EPSS is very low (0.01%), but SSVC rates technical impact as total with automatable exploitation.
Constraint extension stripping in the golang.org/x/crypto SSH agent client (versions prior to 0.52.0) allows remote SSH hosts to use forwarded keys without the destination restrictions the user intended. When clients added keys to a remote agent, extensions such as restrict-destination-v00@openssh.com were silently dropped during serialization, effectively converting scoped keys into unrestricted ones on downstream hosts. No public exploit identified at time of analysis and EPSS is very low (0.02%), but SSVC rates technical impact as total and automatable.
Denial-of-service via unchecked memory allocation in russh (Rust SSH library) versions <= 0.60.2 allows local SSH agent peers to trigger uncontrolled buffer growth by sending oversized frame length values, and in pre-0.58.0 releases the same CryptoVec allocation path was reachable from remote SSH transport and zlib decompression buffers. The flaw stems from CryptoVec performing unchecked capacity growth, unchecked length arithmetic, and unsafe allocation/locking calls including NonNull::new_unchecked on potentially failed allocations, which can abort the process under memory pressure. Publicly available exploit code exists in the form of researcher-supplied PoC tests demonstrating both rejection on patched code and crash behavior on historical versions; no public exploit identified at time of analysis for active campaigns and the issue is not listed in CISA KEV.
Remote code execution in Kopia backup server (≤ 0.22.3) allows unauthenticated attackers to run arbitrary OS commands as the Kopia process user via a single HTTP request to /api/v1/repo/exists when the server is launched with --without-password. Publicly available exploit code exists through the published GHSA advisory and PR diff; no public exploit identified at time of analysis as being weaponized in the wild, but the trivially exploitable vector (CVSS 9.8) and detailed write-up make weaponization straightforward. The bug stems from naive space-splitting of attacker-controlled sshArguments that is fed to exec.CommandContext("ssh"), letting an -oProxyCommand= token trigger $SHELL -c execution before any SSH transport is established.
Path traversal in Pipecat's development runner allows unauthenticated remote attackers to read arbitrary files when the --folder flag is used. The /files/{filename:path} endpoint fails to validate paths containing %2F-encoded directory separators, bypassing Starlette's URL normalization. Fixed in version 1.2.0 with no public exploit identified at time of analysis.
Argument/command injection in OpenSSH before 10.3 lets shell metacharacters embedded in an untrusted username trigger command execution on the SSH-client host. It affects deployments that both feed an attacker-influenced username to the ssh command line and use a non-default ssh_config where %-token expansion (e.g. in ProxyCommand/LocalCommand) is enabled. There is no public exploit identified at time of analysis, EPSS is negligible (0.01%), and it is not in CISA KEV; a fixed release (10.3/10.3p1) is available.
OpenSSH before version 10.3 mishandles the authorized_keys principals option when a principals list is combined with a Certificate Authority that uses certain comma character patterns, allowing authenticated local or remote users to disclose sensitive authorization information or manipulate authentication decisions. This vulnerability affects all OpenSSH versions prior to 10.3p1 and requires authenticated access (PR:L) with non-trivial attack complexity (AC:H), resulting in partial confidentiality and integrity impact. No public exploit code or active exploitation has been identified at time of analysis.
Privilege-escalation exposure in OpenSSH before 10.3 (fixed in 10.3p1) where scp, when run by root using the legacy SCP protocol flag -O and without -p (preserve mode), may write a downloaded file with setuid or setgid bits set, contrary to user expectation. A malicious or compromised SSH server (or a man-in-the-middle on the transfer) could thereby cause an attacker-controlled binary to land on disk as a setuid/setgid-root executable, enabling local privilege escalation when it is later run. There is no public exploit identified at time of analysis, EPSS is very low (0.04%), and CISA SSVC rates exploitation as 'none' though technical impact as 'total'.
SSRF in Soft Serve Git server versions 0.6.0 to 0.11.3 allows authenticated attackers to make requests to internal services. PoC and patch available.
Gogs is an open source self-hosted Git service. [CVSS 8.8 HIGH]
Hardcoded OS credentials in Glory RBG-100 cash recycler systems using ISPK-08 software component. Physical cash handling equipment ships with known default credentials enabling complete system takeover.
SiYuan knowledge management system prior to 3.5.5 has a path traversal in /api/file/copyFile allowing arbitrary file operations on the server.
The Terraform/OpenTofu Proxmox Provider prior to version 0.93.1 contains a path traversal vulnerability in its SSH sudoer configuration documentation that permits attackers to escape directory restrictions using ../ sequences and modify arbitrary files on the system. Public exploit code exists for this vulnerability, affecting users who implement the documented SSH configuration. The vulnerability has been patched in version 0.93.1 and a fix is available.
OpenClaw AI assistant versions prior to 2026.1.29 contain two command injection vulnerabilities: unescaped user input in SSH project paths allows remote code execution on SSH hosts, and insufficient validation of SSH target parameters enables local command execution through malicious flag injection. An attacker can exploit these flaws to achieve arbitrary code execution either remotely via SSH or locally on the system running OpenClaw.
n8n is an open source workflow automation platform. [CVSS 8.1 HIGH]
Ziroom ZHOME A0101 devices running version 1.0.1.0 use hardcoded default credentials in the Dropbear SSH service, enabling unauthenticated remote attackers to gain unauthorized access with high impact to confidentiality, integrity, and availability. Public exploit code exists for this vulnerability, and the vendor has not provided a patch or response. While exploitation requires specific conditions, security professionals should prioritize assessment and credential rotation for affected systems.
Soft Serve self-hosted Git server versions 0.11.2 and below have a critical authentication bypass that allows unauthenticated access to private repositories.
Operation And Maintenance Security Management System versions up to 3.0.12. is affected by command injection (CVSS 8.8).
Stored XSS in Termix File Manager (versions 1.7.0-1.9.0) allows attackers with SSH server access to execute arbitrary JavaScript by uploading malicious SVG files that bypass content sanitization. When a Termix user previews the crafted file, the payload executes within the application context with full access to sensitive operations. Public exploit code exists and no patch is currently available.
GNU Bash through 4.3 bash43-026 does not properly parse function definitions in the values of environment variables, which allows remote attackers to execute arbitrary commands via a crafted. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
freeSSHd.exe in freeSSHd through 1.2.6 allows remote attackers to bypass authentication via a crafted session, as demonstrated by an OpenSSH client with modified versions of ssh.c and sshconnect2.c. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 75.9%.
The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX and Linux, when old-style password. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 25.7%.
Memory exhaustion in OpenSSH's transport-layer decompression path allows an authenticated remote user to grow the memory footprint of the per-connection process by sending a compressed payload that inflates beyond the maximum supported packet size (CVE-2026-110927, CVSS 4.3). The flaw is only reachable when SSH compression has been negotiated on the connection, and per the CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) a valid, authenticated session is required, matching OpenSSH's default delayed-compression behaviour in which zlib activates only after authentication. Impact is confined to availability - memory growth in the handling process with no code execution, integrity, or confidentiality effect - and no public exploit code has been identified at time of analysis and the issue is not in CISA KEV; affected scope per available vendor data is Red Hat Enterprise Linux 6 through 10, OpenShift Container Platform 4, and Red Hat Hardened Images.
OpenSSH deployments with GSSAPI authentication and credential delegation enabled can retain delegated credentials after a failed GSSAPI attempt, potentially allowing a subsequent successful login on the same connection to inherit unauthorized credential state. This flaw (CWE-459) is rated CVSS 4.8 and affects Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. No public exploit identified at time of analysis, and exploitation requires non-default GSSAPI configuration plus a specific sequence of failed then successful login, limiting real-world risk.
An authenticated peer on an OpenSSH connection can recover plaintext belonging to another channel when SSH compression is negotiated, because all channels multiplexed over one connection share a single LZ77 dictionary and chosen-plaintext length analysis exposes the content of a victim channel's traffic. Affected deployments include OpenSSH as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. Severity is medium (CVSS 5.3, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N); exploitation requires authentication and is limited by high attack complexity, the non-default nature of compression in many hardened configurations, and the need for genuinely co-resident attacker and victim channels, and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Command injection in the OpenSSH client allows shell metacharacters placed in a command-line username - specifically '$' or a non-trailing backslash - to reach a shell when the ssh configuration expands the %u token inside a ProxyCommand or Match exec directive, giving arbitrary command execution with the privileges of the account that runs ssh. Reachability is conditional: a default OpenSSH configuration is not affected, and the attack requires a non-default config using %u in those directives plus a username that an attacker can control or influence through a script, wrapper, or application that forwards untrusted input as the username, with a user or process actually initiating the connection (UI:R). Affected builds are OpenSSH as shipped in Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; no public exploit identified at time of analysis. Note the scoring divergence: Red Hat assigns 5.4 (C:L/I:L/A:N), while our independent assessment is higher at CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H because command execution under the invoking account can fully compromise confidentiality, integrity, and availability of that account's data and sessions.
Path traversal in the OpenSSH sftp client enables a malicious or compromised SFTP server to cause files downloaded during an sftp copy to be written outside the local directory the user selected. The flaw is client-side and requires user interaction to initiate the transfer from an untrusted server; it is rated CVSS 6.5 with high integrity impact but no confidentiality or availability impact. No public exploit code or confirmed active exploitation was identified at time of analysis, and Red Hat has published tracking for Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4.
Source-IP misattribution in fail2ban's default sshd filter allows a remote, unauthenticated attacker to have fail2ban ban an arbitrary IP address of their choosing. Because OpenSSH records the offered username verbatim in its log lines and fail2ban 0.10.5 through 1.1.1 (before commit ddd879d22664904ace24e1255ac6571808c58187) accepts an "on <token>" suffix after the parsed host address, an attacker can connect to the SSH service using a username such as "x VICTIM-IP on" and cause subsequent failed-login entries to be attributed to that victim address, resulting in a temporary firewall block against a legitimate user or host. The impact is availability-only (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, base 5.3 Medium) with no confidentiality or integrity loss; no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
This is a genuinely low-priority issue by every available signal, not a high-CVSS alarm. Local privilege retention in OpenSSH sshd-session on obsolete platforms (QNX 6, SCO OpenServer 5) allows an authenticated user to cause sshd-session to run with root privileges when GatewayPorts or StreamLocalForwarding is enabled and the host lacks support for file-descriptor passing and unprivileged PTY allocation. Exploitation is confined to those specific configurations, no public exploit has been identified at time of analysis, and the assessed CVSS is 2.9.
OpenSSH sshd builds compiled against the macOS 27 (or later) SDK silently lose their sandbox, removing a containment layer that normally limits the damage an attacker can do if they manage to compromise or corrupt the sshd process. Only OpenSSH through 10.6 built against that specific SDK is affected, which is far from the default configuration for Linux, BSD, or older-macOS deployments. This is a low-severity defense-in-depth regression rather than a directly exploitable flaw - the sandbox loss causes no impact on its own and only produces harm when chained with a separate exploitable sshd vulnerability that the sandbox would otherwise have contained; no public exploit was identified at time of analysis, and the CVSS 3.1 score (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N) reflects that chaining requirement and high attack complexity.
Misinterpretation of the literal configuration value "none" in sshd in OpenSSH before 10.6 causes the daemon to treat the keyword as a filename instead of as a feature-disable value, yielding limited integrity and availability impact with no confidentiality loss. Per our independent assessment this is a low-severity, low-priority issue despite being in ubiquitous software: exploitation is local only (AV:L), requires high attack complexity (AC:H) and high privileges (PR:H), and depends entirely on an administrator having set an sshd option to the literal string "none" in a non-default configuration, so there is no remote or default-configuration exposure. Exploitation status: no public exploit identified at time of analysis, and the issue is not listed in CISA KEV; the only reference is the upstream OpenSSH 10.6 release notes.
OpenSSH servers prior to 10.6 fail to enforce the 'restrict' keyword in authorized_keys against tunnel (tun/tap) forwarding, letting a user who already holds a restricted key open a forwarding tunnel that the administrator explicitly intended to block. This is a control-bypass rather than an access-control failure: the attacker must already possess a valid SSH key provisioned with 'restrict' (assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N), and the flaw only matters on servers older than 10.6 where tunnel forwarding was the specific capability the keyword was relied on to deny. Impact is limited to integrity (establishing the forwarding channel) with no confidentiality or availability loss, the base score is 2.5, and no public exploit code or CISA KEV activity is identified at time of analysis.
Availability degradation in OpenSSH before 10.6 occurs because sshd and ssh fail to enforce the maximum packet length while decompressing highly compressed SSH data, allowing a peer on a connection with negotiated SSH compression to trigger excessive resource consumption. Exploitation requires compression (zlib or zlib@openssh.com) to be negotiated-often not the case on modern OpenSSH servers where compression is disabled or delayed until after authentication-and an active malicious or compromised SSH peer; the independent assessment scores this as remote, network-reachable, unauthenticated with low availability impact and no confidentiality or integrity impact. No public exploit identified at time of analysis.
ssh-keygen in OpenSSH versions before 10.6 can assign incorrect expiration timestamps to generated certificates when a Daylight Saving Time transition is mishandled, producing a bounded integrity error in the certificate's validity window. The issue is local: it requires a user to run ssh-keygen for certificate creation or signing, and it only manifests around DST changes, with slightly more pronounced effects noted for certain Antarctic time zones. With a CVSS score of 2.5 and no public exploit identified at time of analysis, this is a low-priority correctness bug rather than a remotely exploitable security flaw.
The sshd and ssh components of OpenSSH before 10.6 can be made to negotiate and use the LZ77 dictionary-coder compression scheme, a behavior the 'Crossing the Streams' research (arXiv 2609.07709) identifies as contraindicated because compression-derived information leakage can be measured from an observed session. A remote, unauthenticated attacker who can observe and influence the target connection and repeatedly sample it may recover a limited amount of confidential data, but only where the vulnerable compression mode is actually in use; integrity and availability are unaffected. This is a low-severity, low-priority issue (CVSS 3.1 base 3.7; AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) despite being network-reachable and unauthenticated, because exploitation demands an active compression configuration, a privileged observation vantage point, and sustained measurement - no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Directory traversal in the OpenSSH sftp client before 10.6 can cause files to be written to unintended locations when a user performs a recursive copy operation against an attacker-controlled or compromised SFTP server. Exploitation requires the victim to initiate a recursive transfer such as get -r or put -r, and the malicious server supplies crafted path/filename entries containing traversal components; this is a client-side trust issue, not a flaw in an exposed sshd service. No public exploit identified at time of analysis, and the assessed CVSS 3.1 score is 4.2 with high attack complexity and user interaction required.
Unbounded key-derivation cost parameters in Bouncy Castle for Java before 1.86 allow a denial of service against applications that parse attacker-influenced cryptographic structures: PBKDF2 iteration counts, derived-key lengths, scrypt parallelization factor p, and OpenSSH v1 bcrypt round counts were read straight from untrusted input and used to drive the KDF before any password or MAC verification could reject the data. Affected code paths include the RFC 9579 PBMAC1 MAC calculator builders (JcePBMac1CalculatorBuilder, PKCS12PBEUtils.createPBMac1Calculator reached via PKCS12PfxPdu.isMacValid), the PKCS#8/PKCS#12 scrypt cost guards, the raw JCA PBKDF2 provider, and OpenSSH v1 private-key parsing in Bouncy Castle for Java, LTS (before 2.73.13) and FIPS (bcpkix-fips before 1.0.13 / 2.0.13 / 2.1.13). Impact is availability-only (CVSS:4.0 5.3; assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L): exploitation requires the victim application to passively process a malicious blob and is unauthenticated (PR:N), but no key material or data is exposed, and there is no public exploit identified at time of analysis.
Memory exhaustion in the sshd-sftp component of Apache MINA SSHD (1.0.0 through 2.19.0 and 3.0.0-M1 through 3.0.0-M5) lets an authenticated remote SFTP client crash the server by driving the SFTP v6 check-file-name/check-file-handle extension to build an oversized reply entirely in server memory. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), the session must be authenticated and must negotiate SFTP protocol version 6, and the attacker must point the request at a very large (possibly sparse) file using a tiny block size such as the 256-byte minimum, so that file-size divided by block size yields an enormous number of hashes; availability impact is high while confidentiality and integrity are unaffected. This is a genuine but bounded availability risk with no public exploit identified at time of analysis, and deployments that already cap SFTP message size (typically 256kB, as OpenSSH does) are not exposed.
OpenSSH sshd before version 10.5 fails to enforce the `restrict` keyword in `authorized_keys` against tunnel forwarding, allowing a constrained SSH key holder to establish tun-device tunnels that the administrator explicitly intended to block. The flaw affects all OpenSSH releases prior to 10.5 and is classified as a policy-enforcement bypass with low integrity impact. No active exploitation is confirmed per SSVC (exploitation: none) and the vulnerability is absent from the CISA KEV catalog, placing this firmly in the low-urgency tier despite OpenSSH's near-ubiquitous deployment footprint.
Use-after-free (CWE-416) in OpenSSH's ssh client component affects all releases before version 10.5, triggered when a specific pair of remote-forwarding operations occur concurrently, causing access to freed realloc'd memory. A malicious or compromised SSH server could exploit this race condition against a connecting client to achieve partial information disclosure or limited memory corruption. No public exploit has been identified and CISA SSVC rates exploitation as none with partial technical impact, consistent with the moderate CVSS score of 4.8.
OpenSSH ssh-agent before version 10.5 permits remote execution of agent operations - including adding authentication tokens and using SSH keys - that were architecturally intended to be restricted to local access only. The trust boundary failure stems from a misinteraction between the agent locking mechanism and the session-bind@openssh.com extension, allowing an authenticated remote actor to cross the local/remote privilege boundary. No public exploit has been identified at time of analysis, and SSVC assessment confirms no current exploitation activity; however, the network-accessible vector and ubiquitous deployment footprint of OpenSSH make patching to 10.5 the appropriate response for any environment using agent forwarding.
OpenSSH sshd before version 10.4 fails to consistently enforce its built-in minimum authentication delay, undermining the rate-limiting defense designed to slow credential-guessing attacks against SSH services. All OpenSSH releases prior to 10.4 are affected across all platforms, enabling unauthenticated remote attackers to submit authentication attempts at a rate higher than the daemon intends to permit. No public exploit code has been identified and the vulnerability is absent from CISA KEV; however, the trivial attack complexity combined with OpenSSH's near-universal deployment footprint makes prompt patching appropriate.
OpenSSH sshd before version 10.4 silently ignores the GSSAPIStrictAcceptorCheck configuration directive when the server is integrated with Windows Active Directory, defeating a security control that administrators rely on to enforce GSSAPI acceptor name validation during Kerberos-based SSH authentication. This undocumented behavior means AD-joined SSH servers may accept GSSAPI authentications against unintended Kerberos service principals regardless of how the option is configured, yielding limited confidentiality and integrity impact. No public exploits or active exploitation have been identified; the CVSS AC:H rating reflects the specific environmental prerequisites required for exploitation.
OpenSSH's internal-sftp subsystem silently discards all command-line arguments beyond position 9, allowing authenticated SFTP users to bypass security restrictions that administrators intended to enforce via those later-positioned arguments. All OpenSSH releases before 10.4 are affected when sshd_config supplies more than nine arguments to the internal-sftp subsystem, which is a non-default but legitimate administrative pattern used for directory restriction, read-only enforcement, and umask control. No public exploit has been identified and this vulnerability is not listed in the CISA KEV catalog; however, sites relying on complex internal-sftp argument chains for access policy enforcement face a direct, silent policy bypass.
Path traversal in the scp utility of OpenSSH before 10.4 causes files to be written into the parent directory of the intended destination during remote-to-remote copy operations. The root cause is CWE-23 (Relative Path Traversal): scp fails to canonicalize or sanitize paths when relaying data between two remote hosts, allowing an attacker controlling a malicious endpoint to influence where transferred files land. No public exploit identified at time of analysis, and active exploitation has not been confirmed by CISA KEV; the CVSS AC:H and UI:R metrics significantly constrain real-world exploitability.
Path traversal in the OpenSSH sftp client before version 10.4p1 allows an attacker-controlled server to write downloaded files outside the user's intended target directory when the 'sftp server:/path .' bulk-download syntax is used. Affected are all OpenSSH deployments where users sftp from untrusted or attacker-controlled hosts, which in practice spans virtually every Linux and Unix environment. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, though the ubiquity of OpenSSH elevates aggregate exposure despite the moderate per-instance severity.
OpenSSH's GSSAPI authentication cleanup routine contains a heap out-of-bounds read (CWE-125) triggered when the auth-indicators array lacks a trailing NULL terminator, allowing a remote unauthenticated attacker to crash the SSH authentication path and deny SSH service availability. Exploitation is constrained by high attack complexity (AC:H) due to the non-default Kerberos/GSSAPI configuration requirement, limiting real-world exposure to a minority of deployments. No active exploitation is confirmed (not in CISA KEV), no public exploit code has been identified, and the impact is restricted to partial availability loss with no confidentiality or integrity consequence.
X11 forwarding session hijacking in OpenSSH enables a local unprivileged attacker sharing a Linux client host to intercept and partially manipulate the victim's forwarded X11 display traffic by squatting on the predictable abstract UNIX domain socket name before the SSH client creates it. Affected deployments span OpenSSH packages across Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and OpenShift Container Platform 4. No public exploit code has been identified at time of analysis, but successful exploitation yields high-confidence access to sensitive X11 session data including keystrokes, window contents, and clipboard material.
Client-side Denial of Service in OpenSSH's Diffie-Hellman Group Exchange implementation allows a malicious SSH server to crash connecting clients running in FIPS mode. When a victim initiates an SSH connection to an attacker-controlled server, the server sends crafted DH-GEX group parameters that trigger a double free (CWE-415) during FIPS known-group validation, terminating the client process. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, the constraint that only FIPS-mode clients are affected limits real-world impact to regulated or government environments.
Resource exhaustion in Russh's SSH server identification-string reader allows unauthenticated remote attackers to hold connection setup resources indefinitely during the cleartext pre-authentication phase. Russh versions 0.34.0-beta.1 through 0.60.x used the same permissive identification reader for both client and server roles, failing to cap the number of pre-banner lines a connecting client could send before the SSH identification string - a constraint OpenSSH enforces strictly per RFC 4253. Any application serving SSH via russh is exposed to this pre-auth resource-holding condition. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
OpenSSH before 10.3 fails to confirm connection multiplexing in proxy-mode sessions, allowing local attackers with user interaction to bypass intended access controls and potentially manipulate multiplexed connections. The vulnerability affects OpenSSH versions prior to 10.3p1 and requires local access with user interaction (UI:R) on the affected system; while the CVSS score is low (2.5) and integrity impact is limited, the omission of confirmation mechanisms in proxy-mode multiplexing creates a logic flaw that could enable unauthorized session hijacking or redirection in multi-user environments.
OpenSSH before 10.3 incorrectly interprets ECDSA algorithm specifications in PubkeyAcceptedAlgorithms and HostbasedAcceptedAlgorithms configuration options, allowing authenticated users to authenticate using unintended ECDSA variants. The vulnerability requires authenticated network access and high attack complexity, resulting in a low CVSS score of 3.1 with integrity impact but no confidentiality or availability loss. No public exploit code or active exploitation has been documented.
SCP client implementations across Red Hat Enterprise Linux 6-10 and OpenShift Container Platform 4 are vulnerable to path traversal during file transfer, allowing a malicious SCP server to write files outside the designated working directory and potentially execute arbitrary code or modify system configuration. This vulnerability mirrors CVE-2019-6111 in OpenSSH; unauthenticated remote attackers can exploit it with high user interaction (the victim must initiate an SCP connection to a malicious server), resulting in confidentiality, integrity, and availability compromise. No public exploit code or active exploitation has been confirmed at the time of analysis.
A remote code execution vulnerability (CVSS 6.9) that allows denial of service. Remediation should follow standard vulnerability management procedures. Vendor patch is available.
Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself.
A low‑privileged local attacker who gains access to the UBR service account (e.g., via SSH) can escalate privileges to obtain full system access. This is due to the service account being permitted to execute certain binaries (e.g., tcpdump and ip) with sudo. [CVSS 7.8 HIGH]
Outdated MAC algorithms in SSH implementations for Mrs1000 and Lms1000 device firmware enable network-positioned attackers to tamper with session data integrity without user interaction. An attacker with network access can manipulate transmitted SSH traffic due to the use of cryptographically weak message authentication codes. No patch is currently available for affected devices.
Weak CBC cipher suite implementations in SSH services across SSH, LMS1000, and MRS1000 devices enable network-positioned attackers to observe or modify encrypted SSH traffic without authentication. The vulnerability requires user interaction and network access but poses a confidentiality risk to sensitive communications. No patch is currently available.
Weblate versions up to 5.16.0 contains a vulnerability that allows attackers to an argument injection to `ssh-add` (CVSS 6.6).
There is a misconfiguration vulnerability inside the Infotainment ECU manufactured by BOSCH. The vulnerability happens during the startup phase of a specific systemd service, and as a result, the following developer features will be activated: the disabled firewall and the launched SSH server. [CVSS 6.8 MEDIUM]
A flaw was found in Dropbear. When running in multi-user mode and authenticating users, the dropbear ssh server does the socket forwardings requested by the remote client as root, only switching to the logged-in user upon spawning a shell or performing some operations like reading the user's files. [CVSS 5.4 MEDIUM]
ZOC Terminal 7.25.5 contains a denial of service vulnerability in the private key file input field that allows attackers to crash the application. [CVSS 7.5 HIGH]
With physical access to the device and enough time an attacker can desolder the flash memory, modify it and then reinstall it because of missing encryption.
with the restriction that the password is only randomized if the configured date versions up to 2022. contains a security vulnerability.
Gitlab versions up to 18.6.4 is affected by allocation of resources without limits or throttling (CVSS 5.3).