Quick answers
- Is CVE-2026-35471 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35471 being exploited in the wild.
- How severe is CVE-2026-35471?
- Critical severity, with a CVSS score of 9.8, published 6 April 2026.
- Which products and versions are affected?
- github.com/patrickhener/goshs (Go) SEMVER:introduced=0,fixed=1.1.5-0.20260401172448-237f3af891a9.
- Is there a fix for CVE-2026-35471?
- Yes. github.com/patrickhener/goshs (Go): upgrade to 1.1.5-0.20260401172448-237f3af891a9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35471 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35471?
- Check whether you run github.com/patrickhener/goshs (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/patrickhener/goshs (Go): upgrade to 1.1.5-0.20260401172448-237f3af891a9 or later
go get github.com/patrickhener/goshs@v1.1.5-0.20260401172448-237f3af891a9
Technical details
A path traversal vulnerability exists in the `deleteFile()` function within `httpserver/handler.go`. While the code implements a check for '..' sequences in the URL path, it fails to include a `return` statement after identifying a malicious path. Consequently, the execution flow continues to `os.RemoveAll()`, which processes the unsanitized path. An unauthenticated remote attacker can exploit this by sending a specially crafted GET request with a `?delete` parameter and double-encoded traversal sequences to delete arbitrary files or directories outside the intended webroot. The issue is resolved in version 2.0.0-beta.3.
Affected products
- patrickhener goshs < 2.0.0-beta.3
Identifiers
- CVE-2026-35471
- GHSA-6qcc-6q27-whp8
- GO-2026-5186
Timeline
- 2026-04-01: advisory: GitHub Security Advisory published
- 2026-04-06: disclosed: CVE published to NVD
- 2026-04-06: patched: Fix released in version 2.0.0-beta.3