← Back
CVE-2026-8275
low
CVSS 3.7
Vulnerability in github.com/bettercap/bettercap/v2 (CVE-2026-8275)
Summary
vulnerability in github.com/bettercap/bettercap/v2 (CVE-2026-8275). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.41.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-8275** has been found in github.com/bettercap/bettercap/v2.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade github.com/bettercap/bettercap/v2 to **2.41.7** or later.
If unsure, ask your IT team or search "github.com/bettercap/bettercap/v2 CVE-2026-8275" on the vendor's site.
CVE-2026-8275 (github.com/bettercap/bettercap/v2) — CWE-190 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.41.7` — 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-190) exists in github.com/bettercap/bettercap/v2.
📍 Affected scope
github.com/bettercap/bettercap/v2 — .
🔥 Severity
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.41.7**.
🛡️ 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/bettercap/bettercap/v2' .` 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/bettercap/bettercap/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/bettercap/bettercap/v2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/bettercap/bettercap/v2 to 2.41.7ステージング環境で 2.41.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/bettercap/bettercap/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.41.7"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-8275
- package https://github.com/bettercap/bettercap
- web https://github.com/bettercap/bettercap/issues/1263
- web https://github.com/bettercap/bettercap/pull/1264
- web https://github.com/bettercap/bettercap/commit/3731d5576cffae9eefe3721cd46a40933304129f
- web https://github.com/user-attachments/files/26852847/poc.py
- web https://vuldb.com/submit/811145
- web https://vuldb.com/vuln/362572
- web https://vuldb.com/vuln/362572/cti
- web https://github.com/advisories/GHSA-322p-rrj6-j44g
- web [email protected]
- web https://github.com/bettercap/bettercap/releases/tag/v2.41.7