CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HMedium (5.5) in wireshark wireshark. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExplain CVE-2026-96418 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96418?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96418?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-96418 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-96418 |
| Debian | 13 | wireshark | 4.4.19-0+deb13u1 | DEBIAN-CVE-2026-96418 |
| Debian | 14 | wireshark | 4.6.9-1 | DEBIAN-CVE-2026-96418 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | wireshark | no fix listed | UBUNTU-CVE-2026-96418 |
| openSUSE | Tumbleweed | wireshark | 4.6.9-1.1 | openSUSE-SU-2026:11912-1 |
| Azure Linux | 3 | wireshark | no fix listed | AZL-105021 |
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; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Moderate.
Disable the TIFF protocol dissector in Wireshark or tshark to prevent processing of malformed TIFF packets:
1. In the Wireshark GUI:
Navigate to Analyze -> Enabled Protocols..., search for "TIFF", uncheck the entry, and click OK.
2. When using the command-line utility tshark:
Append the `--disable-protocol tiff` option to the command:
tshark --disable-protocol tiff -r <capture_file>
Caveats:
Disabling this protocol prevents decoding and analyzing TIFF image payloads within packet captures. In addition, avoid opening capture files from untrusted sources, and avoid executing packet analysis utilities under root or privileged accounts. No service restart is required as Wireshark operates as a user-space utility.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | wireshark | Fix deferred | |
| Red Hat Enterprise Linux 6 | wireshark | Not affected | |
| Red Hat Enterprise Linux 7 | wireshark | Not affected | |
| Red Hat Enterprise Linux 8 | wireshark | Not affected | |
| Red Hat Enterprise Linux 9 | wireshark | Not 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-96418.