← Back
CVE-2026-40883
Cross-Site Request Forgery (CSRF) in github.com/patrickhener/goshs (CVE-2026-40883)
Summary
vulnerability in github.com/patrickhener/goshs (CVE-2026-40883). Data can be tampered with by attackers. Exploitable via ``Origin``. Mitigation: upgrade to `2.0.0-beta.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40883** has been found in github.com/patrickhener/goshs.
Attackers can target a specific entry point like ``Origin`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade github.com/patrickhener/goshs to **2.0.0-beta.6** or later.
If unsure, ask your IT team or search "github.com/patrickhener/goshs CVE-2026-40883" on the vendor's site.
CVE-2026-40883 (github.com/patrickhener/goshs) — CWE-352 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Origin` / `Referer` / `DELETED` / `CREATED`
Patched: `2.0.0-beta.6` — 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 ``Origin`` without authentication.
📍 Affected scope
github.com/patrickhener/goshs — . Attack surface: `Origin` / `Referer` / `DELETED` / `CREATED`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **2.0.0-beta.6**.
🛡️ 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/patrickhener/goshs to 2.0.0-beta.6ステージング環境で 2.0.0-beta.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/patrickhener/goshs
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go
github.com/patrickhener/goshs/v2
[{"type":"SEMVER","events":[{"introduced":"2.0.0-beta.4"},{"fixed":"2.0.0-beta.6"}]}]