CVE-2026-62325

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 29, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github Patch Available🟡 PoC Available

goshs SFTP authentication bypass via empty password (incomplete fix of CVE-2026-40884) · Advisory · goshs-labs/goshs · GitHub

https://github.com/goshs-labs/goshs/security/advisories/GHSA-rjrw-mjq6-hpmm
github_release Patch Available

v2.1.4

Patch available: goshs-labs/goshs v2.1.4

https://github.com/goshs-labs/goshs/releases/tag/v2.1.4
github_commit

commit 32f4a0e1790a (goshs-labs/goshs)

Fix landed in goshs-labs/goshs commit 32f4a0e1790a — awaiting tagged release

https://github.com/goshs-labs/goshs/commit/32f4a0e1790a709f722d0f3b2341f139d003180a

Vendor Advisories for CVE-2026-62325(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/patrickhener/goshs/v22.1.32.1.4—
goshs.de/goshs/v22.1.32.1.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 01:49 UTCEG score recompute
  2. 2026-07-30 01:30 UTCEPSS rescore
  3. 2026-07-30 01:30 UTCEPSS rescore
  4. 2026-07-29 14:20 UTCEG score recompute
  5. 2026-07-29 13:58 UTCEG score recompute
  6. 2026-07-28 23:23 UTCEG score recompute
  7. 2026-07-28 22:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-62325?
CVE-2026-62325 is a critical vulnerability published on July 28, 2026. 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…
When was CVE-2026-62325 disclosed?
CVE-2026-62325 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62325 actively exploited?
CVE-2026-62325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62325?
CVE-2026-62325 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-62325?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62325, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62325

Explore →

Is Your Infrastructure Affected by CVE-2026-62325?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs