CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HHigh (8.8) in wireshark wireshark. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2026-95387 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95387?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95387?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-95387 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Wireshark Foundation Wireshark | from 4.6.0 before 4.6.9 |
| Wireshark Foundation Wireshark | from 4.4.0 before 4.4.19 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | wireshark | no fix listed | DEBIAN-CVE-2026-95387 |
| Debian | 13 | wireshark | 4.4.19-0+deb13u1 | DEBIAN-CVE-2026-95387 |
| Debian | 14 | wireshark | 4.6.9-1 | DEBIAN-CVE-2026-95387 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | wireshark | no fix listed | UBUNTU-CVE-2026-95387 |
| Red Hat | enterprise_linux:8::appstream | wireshark, wireshark-cli, wireshark-debuginfo and 2 more | 1:2.6.2-22.el8_10 | RHSA-2026:93627 |
| Red Hat | enterprise_linux:8::crb | wireshark-devel, wireshark-debuginfo, wireshark-debugsource and 1 more | 1:2.6.2-22.el8_10 | RHSA-2026:93627 |
| Red Hat | enterprise_linux:9::appstream | wireshark, wireshark-cli, wireshark-debuginfo and 2 more | 1:3.4.10-14.el9_9 | RHSA-2026:97879 |
| Red Hat | enterprise_linux:9::appstream | wireshark, wireshark-cli, wireshark-debuginfo and 2 more | 1:3.4.10-9.el9_8.5 | RHSA-2026:83546 |
| Red Hat | enterprise_linux:9::crb | wireshark-devel, wireshark-debuginfo, wireshark-debugsource and 1 more | 1:3.4.10-14.el9_9 | RHSA-2026:97879 |
| Red Hat | enterprise_linux:9::crb | wireshark-devel, wireshark-debuginfo, wireshark-debugsource and 1 more | 1:3.4.10-9.el9_8.5 | RHSA-2026:83546 |
| Red Hat | enterprise_linux:10.2 | wireshark, wireshark-cli, wireshark-devel and 3 more | 1:4.4.2-10.el10_2.8 | RHSA-2026:84721 |
| Red Hat | enterprise_linux:10.3 | wireshark, wireshark-cli, wireshark-devel and 3 more | 1:4.4.2-10.el10_3.8 | RHSA-2026:98089 |
| openSUSE | Tumbleweed | wireshark | 4.6.9-1.1 | openSUSE-SU-2026:11912-1 |
| AlmaLinux | 8 | wireshark, wireshark-cli, wireshark-devel | 1:2.6.2-22.el8_10 | ALSA-2026:93627 |
| AlmaLinux | 9 | wireshark, wireshark-cli, wireshark-devel | 1:3.4.10-14.el9_9 | ALSA-2026:97879 |
| AlmaLinux | 9 | wireshark, wireshark-cli, wireshark-devel | 1:3.4.10-9.el9_8.5 | ALSA-2026:83546 |
| AlmaLinux | 10 | wireshark, wireshark-cli, wireshark-devel | 1:4.4.2-10.el10_2.8 | ALSA-2026:84721 |
| AlmaLinux | 10 | wireshark, wireshark-cli, wireshark-devel | 1:4.4.2-10.el10_3.8 | ALSA-2026:98089 |
| Rocky Linux | 8 | wireshark | 1:2.6.2-22.el8_10 | RLSA-2026:93627 |
| Rocky Linux | 9 | wireshark | 1:3.4.10-9.el9_8.5 | RLSA-2026:83546 |
| Rocky Linux | 9 | wireshark, wireshark-cli, wireshark-devel and 3 more | 1:3.4.10-14.el9_9 | RLSA-2026:97879 |
| Rocky Linux | 10 | wireshark | 1:4.4.2-10.el10_2.8 | RLSA-2026:84721 |
| Rocky Linux | 10 | wireshark, wireshark-cli, wireshark-devel and 3 more | 1:4.4.2-10.el10_2.8 | RLSA-2026:98089 |
| Azure Linux | 3 | wireshark | no fix listed | AZL-105030 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.
Red Hat rates this Important.
Red Hat rates this vulnerability as Important rather than Moderate because heap-based memory corruption could permit arbitrary code execution in the context of the user analyzing traffic, rather than being strictly confined to application termination. On Red Hat Enterprise Linux, Wireshark and its associated utilities are not deployed as unattended system daemons by default. Exploitation therefore requires an analyst to actively process an untrusted packet capture file or monitor live traffic on a hostile network segment.
Disable the SPDY protocol dissector in Wireshark or TShark to prevent processing of the vulnerable protocol format.
For TShark command-line usage, pass the protocol disable flag:
```
tshark --disable-protocol spdy -r <capture_file>
```
For persistent configuration across sessions, append the protocol to the disabled protocols file:
```
echo "spdy" >> ~/.config/wireshark/disabled_protos
```
In the Wireshark graphical interface:
1. Navigate to Analyze -> Enabled Protocols...
2. Search for "SPDY" and clear the checkbox.
3. Click OK or Save.
Caveat: Disabling the dissector prevents the decoding and inspection of SPDY protocol streams, treating them as generic TCP or TLS payload. Wireshark must be restarted if it is currently running for configuration changes to take effect. Always ensure capture analysis is conducted with non-privileged user privileges.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | wireshark-1:4.4.2-10.el10_2.8 | Fixed 2026-10-19 | RHSA-2026:84721 |
| Red Hat Enterprise Linux 8 | wireshark-1:2.6.2-22.el8_10 | Fixed 2026-11-02 | RHSA-2026:93627 |
| Red Hat Enterprise Linux 9 | wireshark-1:3.4.10-9.el9_8.5 | Fixed 2026-10-15 | RHSA-2026:83546 |
| Red Hat Enterprise Linux 6 | wireshark | Affected | |
| Red Hat Enterprise Linux 7 | wireshark | 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-95387.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.