GoshsApplication
CVE-2026-40189
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 SimpleHTTPServer written in Go. Prior to 2.0.0-beta.4, goshs enforces the documented per-folder .goshs ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with PUT, upload files with multipart POST /upload, create directories with ?mkdir, and delete files with ?delete inside a .goshs-protected directory. By deleting the .goshs file itself, the attacker can remove the folder's auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability. This vulnerability is fixed in 2.0.0-beta.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 confidencegoshs SimpleHTTPServer enforces .goshs ACL/basic-auth for directory listings and file reads but fails to apply the same authorization checks to state-changing operations (PUT, multipart POST /upload, ?mkdir, ?delete). An unauthenticated attacker can upload files, create directories, and delete the .goshs file itself to remove a folder's authentication policy, subsequently accessing previously protected content without credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GoshsApplication
< 2.0.0= 2.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 versionLocate the goshs binary (e.g., which goshs, ps aux | grep goshs, or check common installation paths like /usr/local/bin/goshs). Run 'goshs --version' or check the binary metadata to determine the installed version number.Affected if The installed version is less than 2.0.0-beta.4 or exactly 2.0.0 (any version before the beta.4 patch).
-
Locate the served directory and ACL configurationIdentify the root directory that goshs is serving (typically via command-line argument like -p or --port with a path, or check running process arguments). Look for a file named '.goshs' in that directory - this file contains ACL/basic-auth configuration.Affected if A .goshs ACL file exists in the served directory, indicating authorization is intended but may not be enforced on vulnerable endpoints.
-
Test upload endpoint without authenticationSend an unauthenticated HTTP PUT or POST request to the /upload endpoint (e.g., curl -X PUT http://<host>:<port>/upload/<filename> with a file body). Observe whether the upload succeeds or returns an authentication error.Affected if The file upload completes successfully without providing credentials, indicating the authorization bypass is present.
-
Test file deletion without authenticationSend an unauthenticated HTTP GET or POST request with the ?delete parameter (e.g., curl 'http://<host>:<port>/?delete=filename'). Observe whether the file is deleted without authentication.Affected if The file is deleted without requiring credentials, indicating the authorization bypass is present.
You are affected if goshs version is less than 2.0.0-beta.4 (or equals 2.0.0) and unauthenticated PUT/POST /upload or ?delete requests succeed on directories that should be protected by .goshs ACL rules.
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 · scoped2.0.0
Upgrade goshs to version 2.0.0-beta.4 or later to implement proper authorization enforcement on all state-changing routes.
2.0.0-beta.4
- Check the currently installed version of goshs using 'goshs --version' or by checking the binary/version info
- Stop the goshs service if it is currently running
- Back up any existing goshs configuration files and data
- Download the fixed version (goshs 2.0.0-beta.4) from the official releases or build from source using the commit f212c4f4a126556bab008f79758e21a839ef2c0f
- Replace the existing goshs binary with the fixed version
- Restart the goshs service
- Verify the fix by attempting to perform state-changing operations (PUT, POST /upload, ?mkdir, ?delete) on a .goshs-protected directory without authentication - these should now be denied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Goshs
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40189 — 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-40189 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