# CVE-2026-8275: bettercap zerogod IPP Service zerogod_ipp_primitives.go ippReadChunkedBody integer coercion

> Remote attackers can trigger an integer coercion error in bettercap's IPP service, potentially causing a denial of service.

- **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:** GHSA-322p-rrj6-j44g, GO-2026-5003, UBUNTU-CVE-2026-8275

## What is CVE-2026-8275?

CVE-2026-8275 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 vulnerability was detected in bettercap up to 2.41.5. Affected by this vulnerability is the function ippReadChunkedBody of the file modules/zerogod/zerogod_ipp_primitives.go of the component zerogod IPP Service. Performing a manipulation results in integer coercion error. The attack can be initiated remotely. The attack is considered to have high complexity. The exploitation appears to be difficult. The exploit is now public and may be used. The patch is named 3731d5576cffae9eefe3721cd46a40933304129f. To fix this issue, it is recommended to deploy a patch.

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

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

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


| 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 |
| `github.com/bettercap/bettercap` | Go | All versions | None |

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

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

## Is CVE-2026-8275 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8275 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-8275 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
- github.com/bettercap/bettercap (Go): affected all versions; no fix listed

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-8275/ (Markdown: https://insights.sbomify.com/CVE-2026-8275/index.md)
```

## Sources

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

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