Application crash via unbounded DCT3 stack write
Published Aug 13, 2026 · Updated Aug 13, 2026
Stack-based buffer overflow in Wireshark 4.6.0 through 4.6.7 allows attackers to crash the application via a malformed Gammu DCT3 trace file. The dct3trace reader advances bufp across repeated l2 data attributes without resetting or bounds-checking it, then hex2bin writes past a 23-byte stack array. Exploitation requires a user to open the crafted file; observed impact is a process crash, with no evidence of arbitrary code execution.
Summary
What happened
Stack-based buffer overflow in Wireshark 4.6.0 through 4.6.7 allows attackers to crash the application via a malformed Gammu DCT3 trace file. The dct3trace reader advances bufp across repeated l2 data attributes without resetting or bounds-checking it, then hex2bin writes past a 23-byte stack array. Exploitation requires a user to open the crafted file; observed impact is a process crash, with no evidence of arbitrary code execution.
The record
- CVE
- CVE-2026-19695
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-121, 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
- dct3trace stack-overflow PoC harnessproof 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