Skip to content
Fencer Vulns
medium 6.5

CVE-2026-66063 json

goshs has a Path Traversal issue

published 2026-07-28 3 mo ago modified 2026-10-23 16 d ago also GHSA-wg2q-39h6-66x9 , GO-2026-6137 , EUVD-2026-50082

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/updown.go multipart upload handler split part.FileName() on / but did not reject .., allowing an unauthenticated upload with filename .. to create a file outside the served tree. This issue is fixed in version 2.1.5.

Patch / fix

  • go goshs.de/goshs/v2 2.1.5-0.20260727065949-f3ef599e4091
  • go github.com/patrickhener/goshs/v2 2.1.5-0.20260727065949-f3ef599e4091
  • 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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

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

Affected products

  • goshs-labs goshs

Classification

Weakness
  • 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.