CVE-2026-0962: Wireshark · Out-of-bounds Write
Affects WiresharkSource CVE Database V5
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
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2026
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 2026-10-25.
What to do
Upgrade Wireshark to 4.6.3 or 4.4.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Wireshark FoundationWireshark | 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
To mitigate CVE-2026-0962, organizations should: 1) Avoid opening untrusted or suspicious packet capture files in affected Wireshark versions. 2) Monitor Wireshark vendor announcements and promptly apply patches or updates once released. 3) Use sandboxing or containerization to run Wireshark, limiting the impact of potential crashes on host systems. 4) Employ network security controls to reduce exposure to malicious SOME/IP-SD traffic, such as filtering or segmentation. 5) Educate users and analysts about the risks of opening unknown capture files and encourage verification of file sources. 6) Consider alternative packet analysis tools temporarily if patching is delayed. 7) Implement robust endpoint protection to detect and block delivery of malicious capture files via email or file shares. These measures collectively reduce the likelihood and impact of exploitation while maintaining operational continuity.
Description
SOME/IP-SD protocol dissector crash in Wireshark 4.6.0 to 4.6.2 and 4.4.0 to 4.4.12 allows denial of service