CVE
Ettercap out-of-bounds heap read in SOCKS5 dissector
Affects Ettercap through 0.8.5.1 only when a SOCKS5 session has accepted username/password authentication. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 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, the network sniffing and man-in-the-middle tool, has a heap out-of-bounds read flaw in its SOCKS5 dissector that an attacker on the same network segment can trigger without logging in or any user action. By sending a crafted SOCKS5 authentication packet that Ettercap observes, the attacker can read up to 255 bytes of heap memory past the buffer, and that data may appear in the captured credentials Ettercap prints and logs.
Original description
Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_socks() in src/dissectors/ec_socks.c that allows network-adjacent attackers to read heap memory via unchecked SOCKS5 username/password lengths. Attackers can send a crafted SOCKS5 authentication packet observed by Ettercap to read up to 255 bytes past the heap buffer, disclosing memory printed and logged as captured credentials.
Who should check
Teams running Ettercap 0.8.5.1 or earlier to capture SOCKS5 traffic on TCP 1080 networks, such as network security monitoring and penetration testing groups.
“Affecting ettercap <= 0.8.5.1”
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-129431 (Ettercap through 0.8.5.1 Heap Out-of-Bounds Read via SOCKS5 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-129431 (entry last updated 2026-11-14):
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 through 0.8.5.1 (source: https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-socks5-dissector)
- The server has accepted the username/password authentication scheme for the SOCKS5 session (source: https://github.com/Ettercap/ettercap/blob/v0.8.5.1/src/dissectors/ec_socks.c#L108-L124)
- A prior server SOCKS5 packet (05 02 or 05 00) must create the session (source: https://github.com/Ettercap/ettercap/pull/1340)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-129431 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129431 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/pull/1340
- https://github.com/Ettercap/ettercap/blob/v0.8.5.1/src/dissectors/ec_socks.c#L108-L124
- https://github.com/Ettercap/ettercap
- https://www.vulncheck.com/advisories/ettercap-through-0.8.5.1-heap-out-of-bounds-read-via-socks5-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-129431
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-129431"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Ettercap ettercap
through 0.8.5.1
Evidence 6
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-129431
Is CVE-2026-129431 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 flaw is a heap out-of-bounds read in Ettercap's dissector_socks() function. It can disclose up to 255 bytes of heap memory past a buffer, and that memory is printed and logged as captured credentials.Source: vulncheck.com, github.com, github.com
Which versions are affected by CVE-2026-129431?
ettercap: through 0.8.5.1.Source: cve.now feed data
Am I affected, and how do I check?
Ettercap through version 0.8.5.1 is in the affected range. The branch is reached only when the server has accepted the username/password scheme for the SOCKS5 session, which needs a prior server 05 02 or 05 00 packet to create the session. To check an installed copy, compare its Ettercap version with 0.8.5.1 and see whether SOCKS5 dissection is in use.Source: vulncheck.com, github.com, github.com
How do I fix CVE-2026-129431?
The checked facts name no fixed version and no vendor patch identifiers, so no upgrade target can be given from them. Check the Ettercap project's advisory or release notes for a fix before relying on any version.Source: vulncheck.com, github.com, github.com