Categories
CVE-2026-50138 high CVSS 8.1

Vulnerability in goshs.de/goshs/v2 (CVE-2026-50138)

Summary

Vulnerability in goshs.de/goshs/v2 (CVE-2026-50138). Confidential information can be exposed externally. Exploitable via goshs. Mitigation: upgrade to 2.1.0 or later.

Original description

The description as published by the source.

goshs is a SimpleHTTPServer written in Go. Prior to version 2.1.0, when goshs is launched with WebDAV enabled (-w), the mode-restriction flags --read-only, --upload-only, and --no-delete are enforced only on the primary HTTP port. The WebDAV port is wired straight to golang.org/x/net/webdav.Handler with no equivalent guard, so an authenticated WebDAV client can PUT, DELETE, MKCOL, MOVE, and COPY despite the operator's stated intent. Version 2.1.0 patches the issue.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-50138 has been found in goshs.de/goshs/v2.
Attackers can target a specific entry point like goshs over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade goshs.de/goshs/v2 to 2.1.0 or later.
If unsure, ask your IT team or search "goshs.de/goshs/v2 CVE-2026-50138" on the vendor's site.

CVE-2026-50138 (goshs.de/goshs/v2) — CWE-284 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: goshs / PUT / DELETE / MKCOL
Patched: 2.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-284) exists in goshs.de/goshs/v2. Attackers reach the vulnerable code path via goshs.

📍 Affected scope

Check the vendor advisory for the affected versions of goshs.de/goshs/v2. Attack surface: goshs / PUT / DELETE / MKCOL.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.1.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'goshs.de/goshs/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'goshs.de/goshs/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で goshs.de/goshs/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade goshs.de/goshs/v2 to 2.1.0

    ステージング環境で 2.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go goshs.de/goshs/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.1.0"}]}]
Go goshs.de/goshs
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details