Skip to content

← Actionable
Low, CVSS 2.9

bettercap Has an Integer Coercion Error in the ippReadChunkedBody Function

CVE-2026-8275GHSA-322p-rrj6-j44g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/bettercap/bettercap/v2 2.41.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.9 · 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 · score source
EPSS
  • CVE-2026-8275: 0.52% estimated exploitation activity in the next 30 days; percentile 44.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A vulnerability was detected in bettercap up to 2.41.5. Affected by this vulnerability is the function ippReadChunkedBody of the file modules/zerogod/zerogodippprimitives.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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-322p-rrj6-j44g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-8275

Advisory: bettercap Has an Integer Coercion Error in the ippReadChunkedBody Function
IDs: CVE-2026-8275, GHSA-322p-rrj6-j44g
Record: https://patchnext.com/advisories/cve-2026-8275 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/bettercap/bettercap/v2 2.41.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/bettercap/bettercap/v2: affected < 2.41.7; fixed in 2.41.7

## Suggested inspection (read-only)
- Go github.com/bettercap/bettercap/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/bettercap/bettercap/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-322p-rrj6-j44g (GitHub-reviewed advisory GHSA-322p-rrj6-j44g lists affected ranges: Go github.com/bettercap/bettercap/v2 >=0 <2.41.7)

Commands are suggestions: review each one before running it.

Loading voting…