# CVE-2026-131855: Ettercap through 0.8.5.1 Heap Out-of-Bounds Read via VNC Dissector


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-131855, GHSA-6x87-3h5x-mc29, GHSA-vphc-c3r7-3mh7, UBUNTU-CVE-2026-131855

## What is CVE-2026-131855?

CVE-2026-131855 is a medium-severity vulnerability in ettercap, published on 17 Nov 2026. 

### Official description

Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_vnc() in src/dissectors/ec_vnc.c that checks total packet length instead of remaining bytes. A malicious VNC server can send the authentication type and challenge in one short packet to leak up to 3 bytes of adjacent heap memory via the logged challenge.

Weakness: CWE-125 (Out-of-bounds Read)

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

1 open source package ship an affected version, including ettercap/ettercap.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `ettercap/ettercap` | GitHub | `pkg:github/ettercap/ettercap` | All versions to 0.8.5.1 | None |

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

No fix has been published for CVE-2026-131855 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-131855 being exploited?

There is no known exploitation of CVE-2026-131855 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131855 is a medium-severity vulnerability in ettercap, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131855 in the wild and no public exploit code.

Affected packages and fixed versions:
- ettercap/ettercap (GitHub): affected all versions up to 0.8.5.1; 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-131855/ (Markdown: https://insights.sbomify.com/CVE-2026-131855/index.md)
```

## Sources

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

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