Code execution via profile ZIP path traversal
Published Sep 29, 2026 · Updated Sep 29, 2026
Path traversal in Wireshark 4.4.0 through 4.4.18 and 4.6.0 through 4.6.8 allows attackers to write outside a profile directory via ZIP import. WiresharkZipHelper::unzip() omits its path-containment check on Windows and accepts relative traversal entries in a crafted configuration-profile ZIP. A user must import the profile; the application can crash, and a file written into the Lua plugin directory can execute on the next launch.
Summary
What happened
Path traversal in Wireshark 4.4.0 through 4.4.18 and 4.6.0 through 4.6.8 allows attackers to write outside a profile directory via ZIP import. WiresharkZipHelper::unzip() omits its path-containment check on Windows and accepts relative traversal entries in a crafted configuration-profile ZIP. A user must import the profile; the application can crash, and a file written into the Lua plugin directory can execute on the next launch.
The record
- CVE
- CVE-2026-96419
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4.0 <4.4.19
- Affected versionversion=4.6.0 <4.6.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Configuration-profile ZIP traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started