# CVE-2026-8276: bettercap MySQL Server mysql_server.go integer coercion

> Remote attackers can trigger integer coercion errors in bettercap's MySQL server module, potentially causing unexpected behavior or crashes.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2026-8276, GHSA-jcqv-2g3v-gm88, GO-2026-5463, UBUNTU-CVE-2026-8276

## What is CVE-2026-8276?

CVE-2026-8276 is a medium-severity vulnerability in bettercap, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-192 (Integer Coercion Error), CWE-189

## Which versions are affected by CVE-2026-8276?

3 open source packages ship an affected version, including github.com/bettercap/bettercap/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bettercap/bettercap/v2` | Go | All versions | 2.41.7 |
| `github.com/bettercap/bettercap/v2` | Go | All versions | 2.41.7 |
| `github.com/bettercap/bettercap/v2` | Go | All versions | 2.41.7 |

## How do I fix CVE-2026-8276?

Upgrade github.com/bettercap/bettercap/v2 to 2.41.7 or later.

## Is CVE-2026-8276 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8276 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8276 and fix it if it is affected.

What it is: CVE-2026-8276 is a medium-severity vulnerability in bettercap, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8276 exists.

Affected packages and fixed versions:
- github.com/bettercap/bettercap/v2 (Go): affected all versions; fixed in 2.41.7
- github.com/bettercap/bettercap/v2 (Go): affected all versions; fixed in 2.41.7
- github.com/bettercap/bettercap/v2 (Go): affected all versions; fixed in 2.41.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8276/ (Markdown: https://insights.sbomify.com/CVE-2026-8276/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8276
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8276
- OSV: https://osv.dev/vulnerability/CVE-2026-8276

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8276/
Summaries are generated and may contain mistakes; the official description above is the record.