cve.bz

CVE-2026-95391 wireshark wireshark: Use After Free

5.5 mediumEPSS 0.10%

Medium (5.5) in wireshark wireshark. EPSS 0.10% estimated probability of exploitation activity in the next 30 days.

On this page
ZigBee ZCL protocol dissector crash in 4.6.0 to 4.6.8 allows denial of service

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.10% (unchanged from 0.10% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-95391 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95391?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95391?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95391 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Wireshark Foundation Wiresharkfrom 4.6.0 before 4.6.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14wireshark4.6.9-1DEBIAN-CVE-2026-95391
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morewiresharkno fix listedUBUNTU-CVE-2026-95391
openSUSETumbleweedwireshark4.6.9-1.1openSUSE-SU-2026:11912-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue will cause a crash in Wireshark with no other security impact. Also, this flaw can only be exploited when malformed packets from a pcap file or the network are processed. Due to these reasons, this vulnerability has been rated with a moderate severity.

Red Hat's mitigation

If the ZigBee ZCL protocol dissector is not being used, it can be disabled via the "Enabled Protocols" dialog box in the Wireshark GUI application. This will also disable the protocol dissector when using "tshark", the command line tool.

See the links below for instructions to disable a protocol in Wireshark, specifically the "Control Protocol Dissection" section and the "disabled_protos" configuration file option.

https://www.wireshark.org/docs/wsug_html_chunked/ChCustProtocolDissectionSection.html

https://www.wireshark.org/docs/wsug_html_chunked/ChAppFilesConfigurationSection.html

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10wiresharkNot affected
Red Hat Enterprise Linux 6wiresharkNot affected
Red Hat Enterprise Linux 7wiresharkNot affected
Red Hat Enterprise Linux 8wiresharkNot affected
Red Hat Enterprise Linux 9wiresharkNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-95391.

References

Check your stackJSON