CVE-2026-6535: Improperly Controlled Sequential Memory Allocation in Wireshark

Q: What is the severity of CVE-2026-6535?

CVE-2026-6535 has been classified as a denial of service vulnerability.

Q: How do I fix CVE-2026-6535?

To fix CVE-2026-6535, upgrade Wireshark to version 4.6.5 or later if using version 4.6.x, or to version 4.4.15 or later if using version 4.4.x.

Q: Which software versions are affected by CVE-2026-6535?

CVE-2026-6535 affects Wireshark versions from 4.6.0 to 4.6.4 and from 4.4.0 to 4.4.14.

Q: What issue does CVE-2026-6535 cause in Wireshark?

CVE-2026-6535 causes a crash in Wireshark's dissection engine due to improperly controlled sequential memory allocation.

Q: Is CVE-2026-6535 exploitable remotely?

CVE-2026-6535 can be exploited remotely, leading to a denial of service condition when processing malicious input.

Published Apr 30, 2026

Updated

Dissection engine zlib 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

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 Wireshark to a version that resolves this vulnerability.
Fixed in 4.6.5

Event History

Apr 30, 2026

CVE Published

via MITRE·05:36 AM

Data Sourced

via MITRE·05:36 AM

RemedyDescriptionSeverityWeakness

Data Sourced

via NVD·07:16 AM

DescriptionSeverityWeaknessAffected Software

Dec 24, 58314

Event

via FIRST·03:48 AM

Frequently Asked Questions

What is the severity of CVE-2026-6535?

CVE-2026-6535 has been classified as a denial of service vulnerability.

How do I fix CVE-2026-6535?