cve.bz

CVE-2026-96416 wireshark wireshark: Heap-based Buffer Overflow

5.5 mediumExploit referenceEPSS 0.1%

Medium (5.5) in wireshark wireshark. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
IEEE 802.11 protocol dissector crash in 4.6.0 to 4.6.8 and 4.4.0 to 4.4.18 allows denial of service

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-96416 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96416?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96416?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96416 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Wireshark Foundation Wiresharkfrom 4.6.0 before 4.6.9
Wireshark Foundation Wiresharkfrom 4.4.0 before 4.4.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12wiresharkno fix listedDEBIAN-CVE-2026-96416
Debian13wireshark4.4.19-0+deb13u1DEBIAN-CVE-2026-96416
Debian14wireshark4.6.9-1DEBIAN-CVE-2026-96416
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morewiresharkno fix listedUBUNTU-CVE-2026-96416
openSUSETumbleweedwireshark4.6.9-1.1openSUSE-SU-2026:11912-1
Azure Linux3wiresharkno fix listedAZL-105042

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

Disable the IEEE 802.11 dissector in Wireshark or avoid processing packet captures from untrusted sources.

1. Dissector configuration:

- In the Wireshark graphical interface, navigate to Analyze -> Enabled Protocols, search for "IEEE 802.11", and deselect it.

- When using command-line tools like TShark, disable the protocol using the `--disable-protocol` flag:

`tshark --disable-protocol wlan -r capture.pcap`

2. Operational controls:

Avoid opening capture files from untrusted sources or capturing live traffic on untrusted wireless networks.

3. Package removal:

If packet analysis tools are not required on the system, remove the package:

`sudo dnf remove wireshark`

Caveats:

Disabling the IEEE 802.11 protocol prevents parsing and decoding of wireless frame structures, leaving traffic presented only as raw payload data. Removing the package removes Wireshark binaries and associated CLI tools.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10wiresharkFix deferred
Red Hat Enterprise Linux 6wiresharkNot affected
Red Hat Enterprise Linux 7wiresharkNot affected
Red Hat Enterprise Linux 8wiresharkNot affected
Red Hat Enterprise Linux 9wiresharkNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-96416.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON