WiresharkApplication
CVE-2026-9759
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedROHC protocol dissector crash in Wireshark 4.6.0 to 4.6.5 and 4.4.0 to 4.4.15 allows denial of service
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA crash vulnerability exists in the ROHC (Robust Header Compression) protocol dissector in Wireshark versions 4.6.0 through 4.6.5 and 4.4.0 through 4.4.15. Processing specially crafted ROHC packets can cause Wireshark to crash, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
WiresharkApplication
>= 4.4.0, < 4.4.16>= 4.6.0, < 4.6.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Wireshark is installedRun 'wireshark --version' or 'tshark --version' from command line, or check your package manager for installed wireshark packagesAffected if Wireshark is not installed on the system
-
Identify the exact Wireshark versionExecute 'wireshark --version' and note the version number displayed (e.g., 'Wireshark 4.6.5')Affected if The version falls within 4.6.0 to 4.6.5 or 4.4.0 to 4.4.15
-
Verify ROHC protocol dissector is presentOpen Wireshark GUI, go to Help > About Wireshark > Plugins, or run 'tshark -G dissectors' and search for 'rohc' in the outputAffected if The ROHC dissector plugin or module is loaded in the installation
-
Confirm vulnerability applicabilityIf Wireshark is installed with a version in the affected ranges and the ROHC dissector exists, the environment is potentially vulnerable when processing ROHC trafficAffected if Both conditions are true: affected version range AND ROHC dissector is available
A user is affected if they have Wireshark version 4.6.0-4.6.5 or 4.4.0-4.4.15 installed with the ROHC dissector present, and they open capture files containing ROHC traffic or intercept such traffic live.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.4.164.6.6
Update Wireshark to a version beyond 4.6.5 or 4.4.15 once patches are available, or avoid opening untrusted capture files containing ROHC traffic until the update is applied.
Wireshark 4.4.16 (for 4.4.x branch) or Wireshark 4.6.6 (for 4.6.x branch)
- Identify your current Wireshark version by running 'wireshark --version' or checking Help > About Wireshark
- If running Wireshark 4.4.x (4.4.0 to 4.4.15), upgrade to version 4.4.16
- If running Wireshark 4.6.x (4.6.0 to 4.6.5), upgrade to version 4.6.6
- Download the updated version from the official Wireshark website (www.wireshark.org) or your system's package manager
- Install the updated version and restart Wireshark
- Verify the fix by confirming the new version number
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9759 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data