CVE
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.
Written by a model from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Original 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.
Who should check
Teams running Ettercap 0.8.5.1 or earlier to monitor MySQL traffic on TCP 3306, with the MySQL dissector enabled
“Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_mysql()”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published1 day
- First seen by cve.now
Affected versions
- Ettercap ettercap
through 0.8.5.1
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-131854
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: cve.now feed data
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: vulncheck.com, github.com
Which versions are affected by CVE-2026-131854?
ettercap: through 0.8.5.1.Source: cve.now feed data
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: vulncheck.com, github.com
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: vulncheck.com, github.com