Skip to main content
VulnerabilityPublished

CVE-2026-131854: ettercap · Out-of-bounds Read

Affects ettercapSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 18 Nov 2026, 00:03 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.16.5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
EttercapettercapAffected
  • <=0.8.5.1
Fixed in–
GitHubettercappkg:github/ettercapOther threatsAffected
  • <=0.8.5.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor the vendor advisory for updates and apply any forthcoming patches promptly. Until a fix is available, avoid using Ettercap with untrusted MySQL servers or clients to reduce exposure. Since this is a client-side vulnerability triggered by malicious MySQL packets, network-level filtering or isolation of untrusted MySQL endpoints may help mitigate risk.

Description

Ettercap versions up to 0.8.5.1 have a heap out-of-bounds read vulnerability in the MySQL dissector component. This flaw occurs because the dissector_mysql() function copies seed and password bytes without proper bounds checking. An attacker controlling a malicious MySQL server or client can exploit this by sending truncated greeting or login packets, causing adjacent heap memory to be leaked via hex-encoded output in the interface and logs.

References

Community reviews

Loading reviews…