# CVE-2026-64863: goshs --no-delete WebDAV MOVE bypass allows file deletion/overwrite

> Attackers can bypass file deletion protections in goshs WebDAV servers to delete or overwrite files when the no-delete feature is enabled.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-hq33-8jgp-8qq3, GO-2026-6136

## What is CVE-2026-64863?

CVE-2026-64863 is a critical missing authorization vulnerability in goshs-labs goshs, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.4, the httpserver/server.go wdGuard handled WebDAV MOVE as a write-only method and did not enforce --no-delete, allowing WebDAV clients to delete or overwrite files via MOVE with Overwrite: T. This issue is fixed in version 2.1.4.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-64863?

11 open source packages ship an affected version, including github.com/patrickhener/goshs, github.com/patrickhener/goshs/v2 and goshs.de/goshs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/patrickhener/goshs` | Go | All versions | None |
| `github.com/patrickhener/goshs` | Go | All versions to 1.1.4 | None |
| `github.com/patrickhener/goshs` | Go | All versions to 1.1.4 | None |
| `github.com/patrickhener/goshs/v2` | Go | All versions | 2.1.4 |
| `github.com/patrickhener/goshs/v2` | Go | All versions | 2.1.4 |
| `goshs.de/goshs` | Go | All versions | None |
| `goshs.de/goshs` | Go | All versions to 1.1.4 | None |
| `goshs.de/goshs` | Go | All versions to 1.1.4 | None |
| `goshs.de/goshs/v2` | Go | All versions | 2.1.4 |
| `goshs.de/goshs/v2` | Go | All versions | 2.1.4 |
| `goshs.de/goshs/v2` | Go | All versions | 2.1.4 |

## How do I fix CVE-2026-64863?

Upgrade to a fixed version.

## Is CVE-2026-64863 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64863 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64863 and fix it if it is affected.

What it is: CVE-2026-64863 is a critical missing authorization vulnerability in goshs-labs goshs, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64863 exists.

Affected packages and fixed versions:
- github.com/patrickhener/goshs (Go): affected all versions; no fix listed
- github.com/patrickhener/goshs (Go): affected all versions up to 1.1.4; no fix listed
- github.com/patrickhener/goshs (Go): affected all versions up to 1.1.4; no fix listed
- github.com/patrickhener/goshs/v2 (Go): affected all versions; fixed in 2.1.4
- github.com/patrickhener/goshs/v2 (Go): affected all versions; fixed in 2.1.4
- goshs.de/goshs (Go): affected all versions; no fix listed
- goshs.de/goshs (Go): affected all versions up to 1.1.4; no fix listed
- goshs.de/goshs (Go): affected all versions up to 1.1.4; no fix listed
- goshs.de/goshs/v2 (Go): affected all versions; fixed in 2.1.4
- goshs.de/goshs/v2 (Go): affected all versions; fixed in 2.1.4
- goshs.de/goshs/v2 (Go): affected all versions; fixed in 2.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64863/ (Markdown: https://insights.sbomify.com/CVE-2026-64863/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64863
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64863
- OSV: https://osv.dev/vulnerability/CVE-2026-64863

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64863/
Summaries are generated and may contain mistakes; the official description above is the record.