Ettercap through 0.8.4.1 Heap Out-of-Bounds Read via TLS SNI Parsing
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- 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 through 0.8.4.1 contains a heap out-of-bounds read vulnerability in sslw_get_clienthello_sni() in src/ec_sslwrap.c that trusts the unchecked 16-bit SNI length field. Network-adjacent attackers can send crafted TLS ClientHello messages during SSL interception to leak up to 64 KB of heap memory upstream or crash Ettercap.
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.2/10CVSS 7.2
- 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Ettercap ettercap
through 0.8.4.1
Evidence 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125402
Is CVE-2026-125402 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?
The bug is an out-of-bounds read in Ettercap's TLS SNI parsing. Reading past the end of a heap buffer can leak nearby heap memory to an attacker-controlled endpoint and can crash Ettercap when the read runs off a mapped page.Source: github.com
Which versions are affected by CVE-2026-125402?
ettercap: through 0.8.4.1.Source: cve.now feed data
Am I affected, and how do I check?
Ettercap versions through 0.8.4.1 are listed as affected. The bug needs SSL MITM to be active and a build with HAVE_OPENSSL_1_1_1 defined, so check whether SSL MITM is enabled in your configuration and whether your build defines that flag.Source: github.com
How do I fix CVE-2026-125402?
No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the Ettercap project for a release newer than 0.8.4.1 that addresses this issue.Source: github.com