Skip to main content
VulnerabilityPublished Updated

CVE-2024-11596: Wireshark · Buffer Over-read

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • =4.4.0
  • =4.2.0
Fixed in–

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

AI-suggested

  1. Upgrade Wireshark to a fixed version once patches are released by the Wireshark Foundation.
  2. Until patches are available, avoid opening untrusted or suspicious capture files and restrict Wireshark usage to trusted environments.
  3. Implement network segmentation and filtering to limit exposure to malicious packet injection, especially on networks where Wireshark is deployed.
  4. Use sandboxing or containerization to isolate Wireshark processes, minimizing impact from crashes or memory exposure.
  5. Educate users and administrators about the risks of opening unknown capture files and encourage verification of file sources.
  6. Monitor network traffic for anomalous ECMP-related packets that could indicate exploitation attempts.
  7. Employ endpoint protection solutions that can detect abnormal application crashes or memory access violations related to Wireshark.

Description

ECMP dissector crash in Wireshark 4.4.0 to 4.4.1 and 4.2.0 to 4.2.8 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…