# CVE-2026-95394: Wireshark Microsoft Network Monitor file parser denial of service

Source: https://junglewise.ai/threats/cve-2026-95394-microsoft-network-monitor-file-parser-large-loop-in-4-6-0-to-4-6  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

CVE-2026-95394 · Severity: medium · CVSS 4.7 · Published 2026-09-29

Wireshark, a network packet analysis tool, contains a flaw in how it processes Microsoft Network Monitor capture files that can cause it to consume excessive CPU resources and become unresponsive. An attacker can craft a malicious 868-byte capture file that forces the application into a lengthy processing loop lasting several seconds per file, preventing normal analysis. This vulnerability can impact organizations that automatically ingest untrusted packet captures or analysts who open suspicious network files.

Technologies: [Wireshark Foundation Wireshark](https://junglewise.ai/threats/technologies/wireshark-foundation-wireshark). Vendors: [Wireshark Foundation](https://junglewise.ai/threats/vendors/wireshark-foundation).

## Quick answers

**Is CVE-2026-95394 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-95394 being exploited in the wild.

**How severe is CVE-2026-95394?** Medium severity, with a CVSS score of 4.7, published 29 September 2026.

**Which products and versions are affected?** Wireshark Foundation Wireshark 4.4.0 to 4.4.18, 4.6.0 to 4.6.8.

**Is there a fix for CVE-2026-95394?** A patch was published on 2026-09-23: Fixed in versions 4.4.19 and 4.6.9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-95394 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-95394?** Check whether you run Wireshark Foundation 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 exists in the NetMon 2.x file parser (wiretap/netmon.c) where timestamp normalization performs unbounded iteration to convert negative nanosecond values one second at a time. An attacker-controlled timestamp delta field can be set to an extreme value (e.g., 1 << 60) causing approximately 9.2 billion loop iterations per packet record. The flaw affects packet capture ingestion services and interactive analysis when processing untrusted files; no user interaction with the packet data itself is required, only opening/reading the file.

## Affected products

- Wireshark Foundation Wireshark 4.4.0 to 4.4.18, 4.6.0 to 4.6.8

## Timeline

- 2026-09-29: disclosed
- 2026-09-23: patched: Fixed in versions 4.4.19 and 4.6.9

## References

- [https://gitlab.com/wireshark/wireshark/-/work_items/21523](https://gitlab.com/wireshark/wireshark/-/work_items/21523)
- [https://www.wireshark.org/security/wnpa-sec-2026-98.html](https://www.wireshark.org/security/wnpa-sec-2026-98.html)

## Related threats

- [Wireshark X11 dissector out-of-bounds heap read](https://junglewise.ai/threats/cve-2026-96423-x11-protocol-dissector-crash-in-4-6-0-to-4-6-8-and-4-4-0-to-4-4)
- [Wireshark Frame protocol metadissector crash](https://junglewise.ai/threats/cve-2026-96422-frame-protocol-metadissector-crash-in-4-6-0-to-4-6-8-and-4-4-0-to)
- [Wireshark Toshiba file parser crash](https://junglewise.ai/threats/cve-2026-96420-toshiba-file-parser-crash-in-4-6-0-to-4-6-8-and-4-4-0-to-4-4-18)
- [Wireshark profile import path traversal code execution](https://junglewise.ai/threats/cve-2026-96419-profile-import-crash-in-4-6-0-to-4-6-8-and-4-4-0-to-4-4-18-allows)
- [Wireshark TIFF dissector infinite loop](https://junglewise.ai/threats/cve-2026-96418-tiff-protocol-dissector-infinite-loop-in-4-6-0-to-4-6-8-and-4-4-0)