CVE-2026-6869: Improperly Controlled Sequential Memory Allocation in Wireshark
Published Apr 30, 2026
·Updated
WebSocket 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
Dec 24, 58314
Event
via FIRST·12:06 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-6869?
The severity of CVE-2026-6869 is medium with a score of 5.5.
2
What is CVE-2026-6869 about?
CVE-2026-6869 involves an improperly controlled sequential memory allocation in Wireshark that can lead to a denial of service.
3
How do I fix CVE-2026-6869?
To fix CVE-2026-6869, upgrade to Wireshark version 4.6.5 or above.
4
What versions of Wireshark are affected by CVE-2026-6869?
CVE-2026-6869 affects Wireshark versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
5
Can CVE-2026-6869 lead to any data breaches?
CVE-2026-6869 does not impact confidentiality or integrity but can lead to a denial of service.