VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/bettercap/bettercap/v2: vulnerability history, versions and safety

github.com/bettercap/bettercap/v2 is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 49 releases, from May 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded L2 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/bettercap/bettercap/v2 vulnerabilities

Vulert verdict on github.com/bettercap/bettercap/v2 v2.41.7 i

Updated on 22 Oct 2026

Action needed: v2.41.7 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v2.41.7 — affected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 3.7 i
  • With no published fix 0 i
  • Stars 20,166 i
  • OpenSSF scorecard 5/10 i
  • Last release 5 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/bettercap/bettercap/v2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v2.41.8-0.20260813134748-8eca2820f3c4 13 Aug 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.8-0.20260811144420-d2afe5445ed9 11 Aug 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.8-0.20260707140805-2359c0be7900 07 Jul 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.8-0.20260521095216-7efbdca333ae 21 May 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.7 11 May 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.6-0.20260418145842-0eaa375c5e54 18 Apr 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.6-0.20260418110212-3731d5576cff 18 Apr 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.6-0.20260408124502-8ab80c10a2f0 08 Apr 2026 L2 U1 GPL-3.0 Yes Details →
v2.41.6-0.20251231153352-d82f62338d49 31 Dec 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5 15 Dec 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20251024224927-b82ce157a425 24 Oct 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20251011140010-ce284d6cb1e2 11 Oct 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20251011134600-a994882e3c1f 11 Oct 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20250928221925-861418a5489c 28 Sep 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20250928221620-620f1d0f3d16 28 Sep 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20250928211948-1e7103fc6958 28 Sep 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20250928160707-afb5d83e1631 28 Sep 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20250920084031-fea84248c0a6 20 Sep 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.5-0.20250823151207-1001cea8f2af 23 Aug 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.4 18 Aug 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.3 18 Aug 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.2 18 Aug 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.2-0.20250809114807-453c417e923d 09 Aug 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1 15 Jul 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250712140406-0216ea69f9f3 12 Jul 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250601114434-948756208af1 01 Jun 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250331181442-84846b11dc3c 31 Mar 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250327123435-9ebd958218f2 27 Mar 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250320180217-6ff2839e153e 20 Mar 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250314231800-cdf870dd4f94 14 Mar 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250302233802-0ea15563b162 02 Mar 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.1-0.20250216125354-4eb923f9723f 16 Feb 2025 L2 U1 GPL-3.0 Yes Details →
v2.41.0 31 Jan 2025 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20250109015551-61a9069e50ea 09 Jan 2025 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20241120133239-c4e45b368dbb 20 Nov 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20241113101726-00854261a45b 13 Nov 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20241010123420-88d813543a04 10 Oct 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20241001124659-e190737c917c 01 Oct 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20240930223754-7e1cb69071b8 30 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20240927184048-ef69151a7f63 27 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20240927182357-ae466b702aa6 27 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.1-0.20240917093237-756dc3d71a31 17 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.40.0 14 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.4.0 13 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.33.1-0.20240901113001-97b4dcb46e84 01 Sep 2024 L2 U1 GPL-3.0 Yes Details →
v2.33.1-0.20240827082830-72afa07d28af 27 Aug 2024 L2 U1 GPL-3.0 Yes Details →
v2.33.1-0.20240823140335-840f81948438 23 Aug 2024 L2 U1 GPL-3.0 Yes Details →
v2.33.1-0.20240818114412-08da91ed5c55 18 Aug 2024 L2 U1 GPL-3.0 Yes Details →
v2.33.1-0.20240809165641-69744e6b6340 09 Aug 2024 L2 U1 GPL-3.0 Yes Details →

All 49 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/bettercap/bettercap/v2

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-8275: bettercap Integer Coercion Error in ippReadChunkedBody Function 3.7 low 2.41.7 11 May 2026
CVE-2026-8276: bettercap Integer Coercion Error in MySQL Server Module 3.7 low 2.41.7 11 May 2026
CVE-2026-8276: Integer Coercion Error in Bettercap MySQL Server Module N/A unrated 2.41.7 24 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About github.com/bettercap/bettercap/v2

Is github.com/bettercap/bettercap/v2 safe to use?

Vulert records 3 vulnerabilities for github.com/bettercap/bettercap/v2 in Go: 0 critical, 0 high, 0 medium and 2 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/bettercap/bettercap/v2's Vulert package health score?

Vulert scores github.com/bettercap/bettercap/v2 83/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/bettercap/bettercap/v2 affected?

Yes. v2.41.7, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/bettercap/bettercap/v2 should I use?

v2.41.7 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/bettercap/bettercap/v2 have?

3 vulnerabilities are recorded for github.com/bettercap/bettercap/v2 in the Go ecosystem: 0 critical, 0 high, 0 medium and 2 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/bettercap/bettercap/v2 vulnerabilities disclosed?

3 vulnerabilities were recorded for github.com/bettercap/bettercap/v2 in the last 12 months, and the oldest entry in this database dates to 11 May 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/bettercap/bettercap/v2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/bettercap/bettercap/v2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/bettercap/bettercap/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.