CVE-2026-76888: Wireshark · Heap-based Buffer Overflow
Affects WiresharkSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low : upgrade to 4.6.8 or 4.4.18 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.6.8, 4.4.18
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade Wireshark to 4.6.8 or 4.4.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Wireshark FoundationWireshark | Affected
| Fixed in
|
| Wireshark FoundationWireshark | Affected
| Fixed in
|
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threats | Affected
| 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 consult the official Wireshark Foundation advisories or update to versions later than 4.4.18 and 4.6.7 once available. Until patches are confirmed, avoid processing untrusted RDP traffic with affected versions to mitigate risk.
Description
A heap-based buffer overflow vulnerability exists in the RDP protocol dissector of Wireshark versions 4.4.0 through 4.4.18 and 4.6.0 through 4.6.7. This flaw can cause the application to crash, resulting in a denial of service condition. The vulnerability has a CVSS score of 3.1, indicating a medium severity level. There is no indication of confidentiality or integrity impact, only availability is affected. No known exploits are reported in the wild.