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.
CVE-2026-66064
MEDIUMPre-NVD 5.35.3—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
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 computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 30, 2026
Advisory Details (3)
Auto-updated Jul 28, 2026Patch available. Sources: github, github_pr, github_commit.
github_commit
commit f3ef599e4091 (goshs-labs/goshs)
Fix landed in goshs-labs/goshs commit f3ef599e4091 — awaiting tagged release
https://github.com/goshs-labs/goshs/commit/f3ef599e409151d1380866e47de8b1afb0bb54fagithub_pr
Fix/sendfile trailingslash upload dotdot
Fix merged in goshs-labs/goshs PR #222 on 2026-07-27 — awaiting tagged release
https://github.com/goshs-labs/goshs/pull/222github Patch Available
ACL Bypass · Advisory · goshs-labs/goshs · GitHub
https://github.com/goshs-labs/goshs/security/advisories/GHSA-964w-f6gj-5236Vendor Advisories for CVE-2026-66064(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 1 ecosystem)
Go(4)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/patrickhener/goshs | — | — | — |
| github.com/patrickhener/goshs/v2 | — | 2.1.5-0.20260727065949-f3ef599e4091 | — |
| goshs.de/goshs | — | — | — |
| goshs.de/goshs/v2 | — | 2.1.5-0.20260727065949-f3ef599e4091 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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.
- 2026-07-30 18:45 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 16:25 UTCEG score recompute
- 2026-07-29 15:33 UTCEG score recompute
- 2026-07-28 23:23 UTCEG score recompute
- 2026-07-28 22:17 UTCEG score recompute
- 2026-07-28 22:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-66064?
CVE-2026-66064 is a medium vulnerability published on July 28, 2026. 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…
When was CVE-2026-66064 disclosed?
CVE-2026-66064 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66064 actively exploited?
CVE-2026-66064 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 76.8% of all scored CVEs.
What is the CVSS score of CVE-2026-66064?
CVE-2026-66064 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-66064?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66064, 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-66064
Is Your Infrastructure Affected by CVE-2026-66064?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.