Skip to main content
CVE-2025-9817VulnerabilityPublished Updated

CVE-2025-9817: Wireshark · NULL Pointer Dereference

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Wireshark Foundation WiresharkAffected
  • =4.4.0
Fixed in–

AI-suggested

1. Immediately avoid opening untrusted or suspicious capture files, especially those containing SSH traffic, until a patch is available. 2. Implement strict file validation and sandboxing measures for analyzing network captures to isolate potential crashes from critical systems. 3. Use alternative packet analysis tools or earlier Wireshark versions not affected by this vulnerability if urgent analysis is required and patching is not yet possible. 4. Monitor Wireshark Foundation announcements for patches addressing this vulnerability and apply updates promptly once released. 5. Educate users and analysts about the risks of opening unverified capture files and enforce policies restricting file sources. 6. Employ network segmentation and access controls to limit exposure of analyst workstations to potentially malicious traffic. 7. Consider automated scanning of capture files for malformed SSH packets before analysis to detect potential exploit attempts. 8. Maintain regular backups of analysis data to prevent loss from unexpected crashes. These measures collectively reduce the risk of exploitation and operational disruption.

Description

SSH dissector crash in Wireshark 4.4.0 to 4.4.8 allows denial of service

References

Community reviews

Loading reviews…