CVE-2026-96421
Improperly Controlled Sequential Memory Allocation in Wireshark
No known exploitation. EPSS puts it in the 2nd percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Wireshark Foundation WiresharkAffected: ≥ 4.6.0, < 4.6.9Upgrade to: 4.6.9Affected: ≥ 4.4.0, < 4.4.19Upgrade to: 4.4.19Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check your installed Wireshark version — vulnerable versions are 4.6.0–4.6.8 and 4.4.0–4.4.18.
- Avoid opening capture files from untrusted or unknown sources until you upgrade.
- Upgrade Wireshark to version 4.6.9 (or 4.4.19 for the older branch) from the official Wireshark site.
- Restart Wireshark after installing the update and confirm the version number changed.
What it is
From the CVE record
USB HID protocol dissector infinite loop and memory leak in 4.6.0 to 4.6.8 and 4.4.0 to 4.4.18 allows denial of service
In plain language
Written by AI from the recordA booby-trapped network capture file can freeze or crash Wireshark, but it can't steal data or take over your computer, and there's no sign anyone is exploiting it yet — still worth updating soon if your team uses Wireshark.
An improperly bounded loop in Wireshark's USB HID dissector (CWE-1325) lets a crafted capture file drive the analyzer into an infinite loop with unbounded memory growth, causing a local denial of service when the file is opened.
If you're affected
- Analysis tool crashes/hangs
- Incident response disrupted
- Memory exhaustion on analyst machine
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.1% chance of exploitation activity in the next 30 days, which ranks it in the 2nd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
10 events over 7 days, from the signal feeds we watch.
- Patch availablerecord updated
- Patch availablepatch available, patch available, published, weakness classified, record updated, record updated, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Scored 5.5 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Wireshark, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI