goshs has ACL Bypass & Path Traversal

published 2026-07-28 3 mo ago modified 2026-10-23 16 d ago also GHSA-964w-f6gj-5236 , GO-2026-6134 , EUVD-2026-50083

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/handler.go sendFile handler opened files using a cleaned path but derived the authorization filename from raw req.URL.Path, so a trailing slash could bypass .goshs ACL-file protection and block-list checks. This issue is fixed in version 2.1.5.

Patch / fix

fixed in 2 distros 2 links 2

go github.com/patrickhener/goshs/v2 2.1.5-0.20260727065949-f3ef599e4091
go goshs.de/goshs/v2 2.1.5-0.20260727065949-f3ef599e4091

suse opensuse

govulncheck-vulndb SLES for SAP applications 16.0, SLES 16.0 0.0.20260827T195228-160000.1.1

suse advisories SUSE-SU-2026:23625-1

govulncheck-vulndb openSUSE Leap 16.0 0.0.20260827T195228-160000.1.1

opensuse advisories openSUSE-SU-2026:21761-1

github.com/goshs-labs/goshs@f3ef599 commit
github.com/goshs-labs/goshs#222 pull request

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 3 mo ago (2026-07-29)

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/patrickhener/goshs/v2	<2.1.5-0.20260727065949-f3ef599e4091	2.1.5-0.20260727065949-f3ef599e4091
go	goshs.de/goshs/v2	<2.1.5-0.20260727065949-f3ef599e4091	2.1.5-0.20260727065949-f3ef599e4091
go	github.com/patrickhener/goshs	<=1.1.4 all versions	no fix listed
go	goshs.de/goshs	<=1.1.4 all versions	no fix listed

Affected products

goshs-labs goshs

Classification

Weakness

CWE-41 Improper Resolution of Path Equivalence
CWE-863 Incorrect Authorization
CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary