Attack Chain

1. An attacker identifies a goshs server running with WebDAV enabled and the --no-delete flag configured (e.g., goshs --webdav --no-delete).
2. The attacker attempts to DELETE a file, which is correctly blocked by the server, returning an HTTP 403 Forbidden status, confirming the --no-delete flag is active for the DELETE verb.
3. The attacker crafts an HTTP MOVE request targeting a sensitive file (e.g., /secret.txt) with a Destination header pointing to a new path (e.g., /gone.txt).
4. The server processes the MOVE request, effectively deleting /secret.txt from its original location and moving its content to /gone.txt, bypassing the --no-delete control.
5. Alternatively, the attacker crafts an HTTP MOVE request with an Overwrite: T header, targeting a source file (e.g., /gone.txt) and a destination path that corresponds to an existing, sensitive file (e.g., /victim.txt).
6. The server processes this MOVE request, first invoking RemoveAll on the existing /victim.txt and then moving the content of /gone.txt to /victim.txt.
7. This results in the original content of /victim.txt being destroyed and replaced with the attacker-controlled content, allowing data destruction or overwriting, despite the --no-delete flag.

Impact

The impact of CVE-2026-64863 is significant for goshs deployments where file integrity and prevention of deletion/overwriting are paramount. If an operator sets up goshs with --no-delete to protect critical data, such as archived artifacts or confidential documents, any authenticated (or unauthenticated, if no ACLs are in place) WebDAV client can exploit this flaw. This allows an attacker to rename confidential files away, effectively deleting them from their expected location, or worse, overwrite existing sensitive files with arbitrary content. This directly violates the intended security posture, leading to data loss, data corruption, or the unavailability of critical information, undermining the trust in the configured security controls.

Recommendation

• Patch CVE-2026-64863: Update goshs to a patched version immediately. Monitor the official GitHub repository for releases that address this vulnerability.
• Deploy the Sigma rule in this brief: Implement the provided Sigma rule into your SIEM to detect suspicious WebDAV MOVE requests, particularly those including the Overwrite: T header.
• Enable webserver logging: Ensure comprehensive logging for your goshs instances, including HTTP method, URI, status codes, and request headers (specifically Overwrite). This is crucial for the provided Sigma rule.