CVE-2026-6867: Improperly Controlled Sequential Memory Allocation in Wireshark
Published Apr 30, 2026
·Updated
SMB2 protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service
Affected Software
3 affected components
Wireshark Wireshark>=4.6.0<=4.6.4, >=4.4.0<=4.4.14
Wireshark Wireshark>=4.4.0<=4.4.14
Wireshark Wireshark>=4.6.0<=4.6.4
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wiresharkto a version that resolves this vulnerability.Fixed in 4.6.5
Event History
Apr 30, 2026
CVE Published
via MITRE·05:33 AM
Data Sourced
via MITRE·05:33 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-6867?
The severity of CVE-2026-6867 is classified as medium with a score of 5.5.
2
What type of vulnerability is CVE-2026-6867?
CVE-2026-6867 is an improperly controlled sequential memory allocation vulnerability in Wireshark.
3
What software versions are affected by CVE-2026-6867?
CVE-2026-6867 affects Wireshark versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
4
How do I fix CVE-2026-6867?
To fix CVE-2026-6867, upgrade to Wireshark version 4.6.5 or above.
5
What can happen if CVE-2026-6867 is exploited?
Exploitation of CVE-2026-6867 can lead to a denial of service by crashing the SMB2 protocol dissector.