Categories
CVE-2026-42091 medium CVSS 6.5

Cross-Site Request Forgery (CSRF) in github.com/patrickhener/goshs (CVE-2026-42091)

Summary

Vulnerability in github.com/patrickhener/goshs (CVE-2026-42091). Data can be tampered with by attackers. Exploitable via e3c3d37. Mitigation: upgrade to 2.0.2 or later.

Original description

The description as published by the source.

goshs is a SimpleHTTPServer written in Go. Prior to version 2.0.2, the PUT upload handler (httpserver/updown.go) lacks the CSRF token validation that was added to the POST upload handler during the CVE-2026-40883 fix. Combined with the unconditional Access-Control-Allow-Origin: * on the OPTIONS preflight handler (httpserver/server.go), any website can write arbitrary files to a goshs instance through the victim's browser — bypassing network isolation (e.g. localhost, internal network). This issue has been patched in version 2.0.2.

Source: NIST National Vulnerability Database 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-42091 has been found in github.com/patrickhener/goshs.
Attackers can target a specific entry point like e3c3d37 over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade github.com/patrickhener/goshs to 2.0.2 or later.
If unsure, ask your IT team or search "github.com/patrickhener/goshs CVE-2026-42091" on the vendor's site.

CVE-2026-42091 (github.com/patrickhener/goshs) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: e3c3d37
Patched: 2.0.2 — 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

CSRF (CWE-352) exists in github.com/patrickhener/goshs. Attackers reach the vulnerable code path via e3c3d37 without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/patrickhener/goshs. Attack surface: e3c3d37.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.0.2.

🛡️ 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 'github.com/patrickhener/goshs' . 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 'github.com/patrickhener/goshs' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade github.com/patrickhener/goshs to 2.0.2

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

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

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

Affected packages

Go github.com/patrickhener/goshs
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.1.4"}]}]
Go goshs.de/goshs
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go goshs.de/goshs/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.0.2"}]}]
Go github.com/patrickhener/goshs/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.0.2"}]}]

References

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