Vulnerability in github.com/bettercap/bettercap/v2 (CVE-2026-8276)
Summary
Vulnerability in github.com/bettercap/bettercap/v2 (CVE-2026-8276). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.41.7 or later.
Original description
The description as published by the source.
A flaw has been found in bettercap up to 2.41.5. Affected by this issue is some unknown functionality of the file modules/mysql_server/mysql_server.go of the component MySQL Server. Executing a manipulation can lead to integer coercion error. The attack can be launched remotely. The attack requires a high level of complexity. The exploitation is known to be difficult. The exploit has been published and may be used. This patch is called 0eaa375c5e5446bfba94a290eff92967a5deac9e. It is advisable to implement a patch to correct this 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-8276 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-8276" on the vendor's site.
CVE-2026-8276 (github.com/bettercap/bettercap/v2) — CWE-192 / 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.
A vulnerability (CWE-192) exists in github.com/bettercap/bettercap/v2.
Check the vendor advisory for the affected versions of github.com/bettercap/bettercap/v2.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 2.41.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/bettercap/bettercap/v2 to 2.41.7ステージング環境で 2.41.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-8276 bettercap
- Ubuntu UBUNTU-CVE-2026-8276 bettercap
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web cna@vuldb.com
- web github.com