Analyzer crash via fixed per-STA array
Published Jan 14, 2026 · Updated Jan 14, 2026
Out-of-bounds write in Wireshark 4.4.0 through 4.4.12 and 4.6.0 through 4.6.2 allows attackers to crash the analyzer. The dissect_multi_link function writes per-STA multi-link subelements into a fixed 16-entry stack array while processing a crafted IEEE 802.11 packet. Exploitation requires injection of a malformed packet onto a monitored network or user interaction to open a malformed capture file, and the demonstrated consequence is a process crash.
Summary
What happened
Out-of-bounds write in Wireshark 4.4.0 through 4.4.12 and 4.6.0 through 4.6.2 allows attackers to crash the analyzer. The dissect_multi_link function writes per-STA multi-link subelements into a fixed 16-entry stack array while processing a crafted IEEE 802.11 packet. Exploitation requires injection of a malformed packet onto a monitored network or user interaction to open a malformed capture file, and the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2026-0959
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 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.13
- Affected versionversion=4.6.0 <4.6.3
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.
Public exploit references
- OSS-Fuzz minimized crash reproducer for issue 20939proof 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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo