CVE-2025-13499: Wireshark · Access of Uninitialized Pointer
Affects WiresharkSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately upgrade Wireshark to a patched version once available from the Wireshark Foundation.
- Until patches are released, avoid opening untrusted or suspicious packet capture files, especially those containing Kafka protocol traffic.
- Implement network segmentation and filtering to limit exposure to untrusted Kafka traffic sources.
- Use sandboxing or isolated environments for analyzing unknown capture files to contain potential crashes.
- Monitor network traffic for anomalous Kafka packets that could be crafted to exploit this vulnerability.
- Educate security analysts and network engineers about the risk and safe handling practices for capture files.
- Consider alternative tools or updated dissectors for Kafka traffic analysis if immediate patching is not feasible.
- Integrate crash monitoring and automated restart mechanisms for Wireshark in critical environments to minimize downtime.
- Maintain up-to-date backups of capture files and analysis configurations to recover quickly from disruptions.
Description
Kafka dissector crash in Wireshark 4.6.0 and 4.4.0 to 4.4.10 allows denial of service