CVE-2026-5656: Wireshark Configuration Profile Import Zip-Slip Path Traversal
- Vendor
- Wireshark Foundation
CVE-2026-5656 is a Zip-Slip path traversal vulnerability in Wireshark’s Configuration Profile import feature. In affected Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14 releases, WiresharkZipHelper::unzip() appends archive entry names to the destination path without ensuring that the resolved extraction path remains within the intended extraction directory. Crafted ZIP entries containing traversal components can therefore cause file creation or overwrite outside the profile-import extraction root. The flaw is classified as CWE-22.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker can cause Wireshark to write attacker-controlled files to locations accessible to the user running Wireshark, resulting in denial of service and potentially code execution. On POSIX systems, arbitrary file write can be escalated by placing a malicious Lua plugin in Wireshark’s user plugin location; Wireshark loads such plugins at startup, causing code execution in the context of that user when the application is relaunched. The documented CVSS v3 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.8).
Mitigation
If you can’t patch tonight, do this now.
Do not import configuration-profile ZIP archives from untrusted or unverifiable sources. Restrict who can provide profile archives to users, and execute Wireshark with least privilege. Where operationally feasible, disable or limit use of profile imports until patched. Monitor for unexpected additions or modifications to user-level Wireshark plugin locations, particularly Lua plugins.
Remediation
Patch, then assume compromise.
Upgrade Wireshark to a fixed release: version 4.6.5 or later on the 4.6 release branch, or version 4.4.15 or later on the 4.4 release branch. The extraction implementation should canonicalize the destination directory and verify, before creating directories or writing each archive entry, that the resolved absolute output path remains beneath that canonical directory.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-5656 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-5656 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-5656?
- Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-5656.
- Is there a patch for CVE-2026-5656?
- Upgrade Wireshark to a fixed release: version 4.6.5 or later on the 4.6 release branch, or version 4.4.15 or later on the 4.4 release branch. The extraction implementation should canonicalize the destination directory and verify, before creating directories or writing each archive entry, that the resolved absolute output path remains beneath that canonical directory.
- What products are affected by CVE-2026-5656?
- Wireshark Foundation Wireshark.
- How severe is CVE-2026-5656?
- CVE-2026-5656 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.18% (8th percentile) as of Sep 25, 2026.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.