Process crash via oversized phtoleu16 write
Published Aug 13, 2026 · Updated Aug 13, 2026
Out-of-bounds write in Wireshark 4.6.0 through 4.6.7 allows attackers to crash Windows builds via a malformed capture file. The optimized phtoleu16 helper in wsutil/pint.h copies four bytes from a 32-bit value even though callers allocate and advance only two bytes. A user must open or process attacker-supplied capture data on an MSVC or Intel-compiled Windows build; the demonstrated consequence is a process crash, not code execution.
Summary
What happened
Out-of-bounds write in Wireshark 4.6.0 through 4.6.7 allows attackers to crash Windows builds via a malformed capture file. The optimized phtoleu16 helper in wsutil/pint.h copies four bytes from a 32-bit value even though callers allocate and advance only two bytes. A user must open or process attacker-supplied capture data on an MSVC or Intel-compiled Windows build; the demonstrated consequence is a process crash, not code execution.
The record
- CVE
- CVE-2026-19696
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 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.6.0 <4.6.8
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
No public exploit references are available in this record.
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