External risk intelligence

Goshs SFTP Unauthenticated File Access Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-62325

The product is a file server tool designed for hosting and transferring files. As a network-accessible file server, it is commonly deployed as an externally reachable service or API endpoint to facilitate file sharing, making it likely to have public-internet-facing exposure in standard usage.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability was discovered in a file server tool that could allow unauthorized access to files if specific authentication settings were not configured. This exposure could potentially impact data confidentiality and integrity, depending on how the tool is deployed and used within an organization. The primary concern at this time is to confirm if this tool is in use and if it is configured in a way that makes it vulnerable.

  • Unauthenticated access to file server data.
  • Potential for unauthorized data access and modification.
  • Verify usage and exposure of this specific file server.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by targeting a vulnerable goshs file server exposed to the network. By sending unauthenticated requests to the SFTP server, an attacker could bypass authentication. This could allow an attacker to access and potentially modify files on the server.

  • Network access required.
  • Unauthenticated SFTP requests trigger.
  • Unauthorized file access and modification risk.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, this vulnerability could allow unauthenticated access to file system data. The affected component improperly handles authentication credentials, permitting unauthorized users to bypass security checks and access files when the server is configured with specific command-line arguments.

  • Unauthorized access to file system data.
  • Unauthenticated access via SFTP.
  • Data exposure and potential modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams responsible for the goshs file server should prioritize identifying all instances of the affected software. Once located, confirm network exposure and business criticality to establish an accurate risk assessment before planning remediation activities, potentially involving vendor coordination or temporary risk reduction if immediate patching is not feasible.

  • Application owners/Infrastructure teams own this issue.
  • Verify network reachability and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is goshs and how is it used?

goshs is a lightweight, single-binary file server utility frequently utilized by developers and red teamers to quickly host and transfer files across network environments.

What does CVE-2026-62325 mean for security?

This vulnerability is classified as Missing Authentication for Critical Function (CWE-306). It means the software fails to verify user identities before granting access to files, effectively allowing anyone with network access to interact with the file server without providing a valid password.

How can an attacker trigger this vulnerability?

The flaw occurs specifically when the server is started with command-line arguments that leave the SFTP authentication handlers unset. The vulnerability is not triggered if standard authentication is correctly configured or if the SFTP component is disabled entirely.

Is my goshs instance at risk?

Halo Surface Signal indicates that because goshs is designed for file sharing, it is frequently deployed as an internet-facing service. If your instance is reachable over a public network, it is at higher risk of unauthorized access compared to a service restricted to internal segments.

How do I secure my environment against this?

The first step is to identify all running instances of goshs in your infrastructure. Verify their network accessibility and immediately upgrade any affected versions to 2.1.4, which includes the necessary fix to properly enforce password authentication.

References