Quick answers
- Is CVE-2026-19696 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19696 being exploited in the wild.
- How severe is CVE-2026-19696?
- Medium severity, with a CVSS score of 6.6, published 13 August 2026.
- Which products and versions are affected?
- Wireshark 4.6.0 to 4.6.7.
- Is there a fix for CVE-2026-19696?
- A patch was published on 2026-08-13: Fix released in Wireshark 4.6.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19696 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-19696?
- Check whether you run Microsoft Windows or Wireshark at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an out-of-bounds write (CWE-787) in the optimized MSVC/Intel implementation of the `phtoleu16()` helper function in `wsutil/pint.h`. The function is documented and used as a 2-byte little-endian store but uses a 32-bit parameter and calls `memcpy(p, &v, sizeof(v))` which copies 4 bytes. The bug affects only MSVC without clang-cl, Intel Classic, or Intel LLVM builds; GCC/Clang portable implementations are unaffected. Attack vectors include parsing malformed VWR S3 WLAN RF capture files and NetMon format exports; callers also include RTP audio export functionality. The overflow is deterministic on affected builds and can corrupt stack or heap-allocated 2-byte objects. A patch changing the parameter to `uint16_t` and using `sizeof(v)` correctly fixes the issue. Wireshark 4.6.8 or later resolves this.
Affected products
- Wireshark Wireshark 4.6.0 to 4.6.7
Timeline
- 2026-08-12: disclosed
- 2026-08-13: patched: Fix released in Wireshark 4.6.8