WiresharkApplication
CVE-2026-3202
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 · uneditedNTS-KE protocol dissector crash in Wireshark 4.6.0 to 4.6.3 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 · moderate confidenceA crash vulnerability exists in the NTS-KE (Network Time Security - Key Exchange) protocol dissector in Wireshark versions 4.6.0 through 4.6.3. The dissector fails to properly handle certain malformed packets, causing Wireshark to crash when processing or analyzing capture files containing malicious NTS-KE traffic.
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.6.0, < 4.6.4CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 'wireshark -v' from a command prompt or terminalAffected if Command fails or Wireshark is not found - not affected; if Wireshark responds, note the version number for next step
-
Determine the installed Wireshark versionLocate the version number in the output from the version check commandAffected if Version output shows a number you can compare to the affected range (>= 4.6.0 and < 4.6.4)
-
Compare your version to the affected rangeCheck if your installed version falls within 4.6.0 through 4.6.3 inclusiveAffected if Your version is 4.6.0, 4.6.1, 4.6.2, or 4.6.3 - you are running a vulnerable version
-
Verify NTS-KE protocol handling is possibleAttempt to open a capture file containing NTS-KE traffic or capture live traffic with Wireshark, or check if the NTS-KE dissector is loadedAffected if You can process NTS-KE packets and your Wireshark version is in the affected range - you are vulnerable to the crash
You are affected if Wireshark version 4.6.0, 4.6.1, 4.6.2, or 4.6.3 is installed and you process NTS-KE traffic or open capture files containing NTS-KE packets.
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.6.4
Upgrade Wireshark to version 4.6.4 or later. Avoid opening untrusted packet capture files or live capture from untrusted network segments until the update is applied.
Wireshark 4.6.4
- 1. Verify current Wireshark version by checking Help > About Wireshark
- 2. Download Wireshark 4.6.4 or later from the official website (https://www.wireshark.org/download.html)
- 3. Uninstall the current Wireshark version
- 4. Install the downloaded Wireshark 4.6.4 or later version
- 5. Restart Wireshark and verify the version is 4.6.4 or higher
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-3202 — 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-3202 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