CVE-2026-6533: Improperly Controlled Sequential Memory Allocation in Wireshark
Dissection engine LZ77 decompression crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service
Affected Software
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
Frequently Asked Questions
What is the severity of CVE-2026-6533?
CVE-2026-6533 is categorized as a denial of service vulnerability due to improper memory allocation in Wireshark.
How do I fix CVE-2026-6533?
To resolve CVE-2026-6533, update Wireshark to version 4.6.5 or later to ensure the vulnerability is patched.
Which versions of Wireshark are affected by CVE-2026-6533?
CVE-2026-6533 affects Wireshark versions 4.6.0 through 4.6.4 and versions 4.4.0 through 4.4.14.
What causes the CVE-2026-6533 vulnerability?
CVE-2026-6533 is caused by improperly controlled sequential memory allocation within the Wireshark dissection engine during LZ77 decompression.
What impact does CVE-2026-6533 have on systems running Wireshark?
CVE-2026-6533 can lead to a denial of service, crashing affected systems that utilize the vulnerable versions of Wireshark.