Skip to main content
CVE-2026-0959VulnerabilityPublished Updated

CVE-2026-0959: Wireshark · Out-of-bounds Write

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.6.3 or 4.4.13 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.6.3, 4.4.13
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2026

  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

Upgrade Wireshark to 4.6.3 or 4.4.13.

Affected software

ProductAffectedFixed in
Wireshark FoundationWiresharkAffected
  • >=4.6.0 <4.6.3
  • >=4.4.0 <4.4.13
Fixed in
  • 4.6.3
  • 4.4.13
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • =4.6.0
  • =4.4.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should monitor Wireshark Foundation announcements and promptly apply patches once released for versions 4.4.x and 4.6.x. If you cannot patch yet, users can mitigate risk by disabling the IEEE 802.11 dissector if not required for their analysis tasks, thereby preventing processing of malicious packets targeting this vulnerability. Additionally, security teams should avoid opening untrusted capture files or capturing traffic from untrusted wireless networks without proper filtering. Employing network segmentation and limiting exposure of systems running Wireshark to untrusted networks can reduce attack surface. Training analysts to recognize suspicious capture files and maintaining updated endpoint protection can further reduce risk. Finally, consider using alternative packet analysis tools or earlier stable Wireshark versions not affected by this vulnerability if immediate patching is not feasible.

Description

IEEE 802.11 protocol dissector crash in Wireshark 4.6.0 to 4.6.2 and 4.4.0 to 4.4.12 allows denial of service

References

Community reviews

Loading reviews…