CVE-2026-76887Network attack vector

Crash via wrapped reassembly length accumulation

Published Aug 19, 2026 · Updated Aug 20, 2026

Heap-based buffer overflow in Wireshark 4.6.0 through 4.6.7 and 4.4.0 through 4.4.17 allows attackers to crash the process via crafted input. In epan/reassemble.c, fragment_defragment_and_free() adds fragment lengths into a 32-bit size, allocates g_malloc(size) after wraparound, and then copies each fragment at full fd_i->len into the undersized heap buffer. Reachability is limited to block-sequence reassembly paths; the public report proves SMTP, DICOM, and WebSocket cases and requires more than 4 GiB of genuine fragment data, so the published impact is a bounded denial of service rather than demonstrated code execution.

CVSS severity3.1
Low
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap-based buffer overflow in Wireshark 4.6.0 through 4.6.7 and 4.4.0 through 4.4.17 allows attackers to crash the process via crafted input. In epan/reassemble.c, fragment_defragment_and_free() adds fragment lengths into a 32-bit size, allocates g_malloc(size) after wraparound, and then copies each fragment at full fd_i->len into the undersized heap buffer. Reachability is limited to block-sequence reassembly paths; the public report proves SMTP, DICOM, and WebSocket cases and requires more than 4 GiB of genuine fragment data, so the published impact is a bounded denial of service rather than demonstrated code execution.

The record

CVE
CVE-2026-76887
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
Wireshark Foundation
Product
Wireshark
Classifications
CWE-122, T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.4.0 <4.4.18
  2. Affected versionversion=4.6.0 <4.6.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Wireshark Foundation · Wiresharkversion=4.4.0 <4.4.18; version=4.6.0 <4.6.8

Published CVSS scores

3.1GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-122Heap-based Buffer Overflow
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo