CVE-2026-64863
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedgoshs 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn goshs prior to 2.1.4, the wdGuard function in httpserver/server.go incorrectly handled WebDAV MOVE operations as write-only and failed to enforce the --no-delete flag. This allowed WebDAV clients to bypass delete restrictions by using the Overwrite: T header in MOVE requests, enabling unauthorized file deletion or overwriting.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify goshs installation and versionRun 'goshs --version' or check the binary version if installed, or inspect the running process/container image tagAffected if Version is present and is prior to 2.1.4
-
Confirm WebDAV is enabledInspect the goshs startup command or configuration for WebDAV-related flags such as --webdav, or check if port 80/443 is serving WebDAV endpointsAffected if WebDAV is actively enabled and accessible
-
Verify --no-delete flag configurationReview the goshs startup flags or config file to determine if --no-delete is configured for the WebDAV serviceAffected if --no-delete flag is set (the intended protection that is bypassed by the vulnerability)
-
Test MOVE request behavior with Overwrite headerSend a WebDAV MOVE request with 'Overwrite: T' header to an existing file via an authenticated WebDAV client (curl -X MOVE -H 'Overwrite: T' -u user:pass source dest)Affected if The MOVE request successfully overwrites or deletes the target file despite --no-delete being enabled
The environment is affected if running goshs version prior to 2.1.4 with WebDAV enabled and the --no-delete flag configured, as MOVE requests can bypass deletion prevention controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade goshs to version 2.1.4 or later to obtain the patch. If immediate patching is not feasible, restrict or disable WebDAV access and monitor for suspicious MOVE requests with Overwrite headers.
2.1.4
- Check current goshs version by running 'goshs --version' or checking the binary
- Download goshs version 2.1.4 from the official releases (github.com)
- Replace the existing goshs binary with the version 2.1.4 binary
- Verify the new version is installed by running 'goshs --version'
- Restart the goshs service if it is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-64863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-64863 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data