CVE-2026-96416
Received Received - Intake

IEEE 802.11 Protocol Dissector DoS in Wireshark

Vulnerability report for CVE-2026-96416, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-29

Last updated on: 2026-09-29

Assigner: GitLab Inc.

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-29
Last Modified
2026-09-29
Generated
2026-09-29
AI Q&A
2026-09-29
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
wireshark wireshark From 4.4.0 (inc) to 4.4.18 (inc)
wireshark wireshark From 4.6.0 (inc) to 4.6.8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-96416 is a vulnerability in Wireshark's IEEE 802.11 protocol dissector that causes a crash due to a length desynchronization between two Fast BSS Transition (FT) elements in 802.11 management frames. When Wireshark's decryption feature is enabled, a crafted frame with two FT elements can trigger a negative length value, leading to an out-of-bounds read in libgcrypt and crashing the application.

Detection Guidance

To detect this vulnerability, monitor for crashes in Wireshark or tshark when analyzing WPA traffic with decryption enabled. Look for malformed IEEE 802.11 management frames with two Fast BSS Transition elements. Use Wireshark versions 4.6.0 to 4.6.8 or 4.4.0 to 4.4.18 to check for crashes during packet capture or trace file analysis.

Impact Analysis

This vulnerability can cause Wireshark or tshark to crash, resulting in a denial of service. It may be exploited by injecting a malformed packet into the network or tricking a user into opening a malicious packet trace file. Users analyzing WPA traffic with decryption enabled are particularly affected.

Compliance Impact

This vulnerability primarily causes a denial of service by crashing Wireshark, which could disrupt network monitoring and analysis activities. For compliance with standards like GDPR or HIPAA, continuous monitoring and logging are often required. A crash could lead to gaps in logging or monitoring, potentially violating record-keeping or audit requirements if critical network traffic is not captured or analyzed.

Mitigation Strategies

Upgrade Wireshark to version 4.6.9 or later, or 4.4.19 or later. Avoid opening untrusted packet trace files. Disable Wireshark's decryption feature if not required. Monitor network traffic for suspicious IEEE 802.11 management frames with two FT elements.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-96416. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart