# CVE-2026-62325: goshs SFTP authentication bypass via empty password (incomplete fix of CVE-2026-40884)

> Attackers can bypass SFTP authentication and access files when specific command-line flags are used without a key file.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-rjrw-mjq6-hpmm, GO-2026-6132

## What is CVE-2026-62325?

CVE-2026-62325 is a critical authentication bypass vulnerability in goshs-labs goshs, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

goshs is a feature-rich single-binary file server for red teamers and developers. From 2.1.3 until 2.1.4, the sftpserver/sftpserver.go password handler used Username != "" && Password != "", so running goshs with -b 'admin:' -sftp and no -fkf left both SFTP authentication handlers unset and allowed unauthenticated file access. This issue is fixed in version 2.1.4.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-62325?

6 open source packages ship an affected version, including goshs.de/goshs/v2, github.com/patrickhener/goshs/v2 and goshs.de/goshs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `goshs.de/goshs/v2` | Go | From 2.1.3 | 2.1.4 |
| `goshs.de/goshs/v2` | Go | From 2.1.3 | 2.1.4 |
| `goshs.de/goshs/v2` | Go | From 2.1.3 | 2.1.4 |
| `github.com/patrickhener/goshs/v2` | Go | From 2.1.3 | 2.1.4 |
| `github.com/patrickhener/goshs/v2` | Go | From 2.1.3 | 2.1.4 |
| `goshs.de/goshs` | Go | All versions | None |

## How do I fix CVE-2026-62325?

Upgrade goshs.de/goshs/v2 to 2.1.4 or later.

## Is CVE-2026-62325 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62325 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62325 and fix it if it is affected.

What it is: CVE-2026-62325 is a critical authentication bypass vulnerability in goshs-labs goshs, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62325 exists.

Affected packages and fixed versions:
- goshs.de/goshs/v2 (Go): affected from 2.1.3; fixed in 2.1.4
- goshs.de/goshs/v2 (Go): affected from 2.1.3; fixed in 2.1.4
- goshs.de/goshs/v2 (Go): affected from 2.1.3; fixed in 2.1.4
- github.com/patrickhener/goshs/v2 (Go): affected from 2.1.3; fixed in 2.1.4
- github.com/patrickhener/goshs/v2 (Go): affected from 2.1.3; fixed in 2.1.4
- goshs.de/goshs (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62325/ (Markdown: https://insights.sbomify.com/CVE-2026-62325/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62325
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62325
- OSV: https://osv.dev/vulnerability/CVE-2026-62325

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62325/
Summaries are generated and may contain mistakes; the official description above is the record.