Skip to main content
CVE-2026-0961VulnerabilityPublished Updated

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

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 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.5Medium
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.
Patch
Available – fixed in 4.6.3, 4.4.13
CVSS:3.1/AV:L/AC:L/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

To mitigate CVE-2026-0961, organizations should: 1) Avoid opening BLF files from untrusted or unknown sources until patches are released. 2) Monitor official Wireshark Foundation channels for security updates and apply patches promptly once available. 3) Implement strict file handling policies and user training to reduce the risk of opening malicious files. 4) Use sandboxing or isolated environments when analyzing suspicious BLF files to contain potential crashes. 5) Employ endpoint protection solutions that can detect anomalous application crashes or suspicious file activity. 6) Consider alternative network analysis tools if immediate patching is not possible and BLF file analysis is critical. 7) Maintain regular backups of critical analysis data and configurations to minimize operational impact from DoS events. These steps go beyond generic advice by emphasizing cautious file handling, environment isolation, and proactive monitoring specific to this vulnerability's characteristics.

Description

BLF file parser 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…