Skip to main content
Mallory
LowPublic exploitVulnerability

CVE-2026-8276: Remote Denial of Service in bettercap MySQL Server

Published May 11, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS2.9Low · v4
EPSS0.39%34th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-8276CWE-192 · Integer Coercion Error

CVE-2026-8276 is an integer coercion error in bettercap through version 2.41.5 in the MySQL Server component. A remote attacker can submit a crafted MySQL client handshake that reaches the affected processing logic and triggers a denial-of-service condition.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can remotely deny service in bettercap's MySQL Server component, disrupting its availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the bettercap MySQL Server component by disabling the MySQL Server functionality if it is not required, or restricting network access to trusted hosts only. Because the issue is remotely reachable, limiting access paths and isolating the service can reduce exploitability until the patch is applied. No vulnerability-specific workaround beyond patching is provided in the available information.

Remediation

Patch, then assume compromise.

Apply the upstream fix for CVE-2026-8276 or upgrade to a bettercap package release incorporating that fix. Debian 13.7 includes a correction for the vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-8276 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-8276 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-8276?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-8276.
Is there a patch for CVE-2026-8276?
Apply the upstream fix for CVE-2026-8276 or upgrade to a bettercap package release incorporating that fix. Debian 13.7 includes a correction for the vulnerability.
How severe is CVE-2026-8276?
CVE-2026-8276 has a CVSS v4 score of 2.9 (Low) and an EPSS score of 0.39% (34th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.