WiresharkApplication
CVE-2026-15173
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 · uneditedpcapng file parser crash in Wireshark 4.6.0 to 4.6.6 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 denial of service vulnerability exists in the pcapng file parser of Wireshark versions 4.6.0 through 4.6.6. Processing a specially crafted pcapng file triggers a crash in the parser, causing Wireshark to terminate unexpectedly.
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.7CVSS 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.
-
Verify Wireshark is installedRun 'wireshark --version' on command line, or check Help > About Wireshark in the GUI, or run 'dpkg -l wireshark' (Linux) / 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName, DisplayVersion' (Windows)Affected if Wireshark is present on the system
-
Identify the installed Wireshark versionParse the version number from the version check command output - look for a version like 4.6.xAffected if A version number is returned
-
Compare version to affected rangeCheck if the version falls between 4.6.0 and 4.6.6 inclusive (versions 4.6.0, 4.6.1, 4.6.2, 4.6.3, 4.6.4, 4.6.5, or 4.6.6)Affected if The installed version is 4.6.0 through 4.6.6
The environment is affected if Wireshark version 4.6.0 through 4.6.6 is installed, since the pcapng parser vulnerability exists in those versions.
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.7
Update Wireshark to version 4.6.7 or later. Avoid opening untrusted pcapng files from unknown sources until the update is applied.
Wireshark 4.6.7
- 1. Close Wireshark if it is currently running
- 2. Check your current Wireshark version by running 'wireshark --version' or checking Help > About Wireshark
- 3. Download Wireshark 4.6.7 from the official Wireshark website (www.wireshark.org) or your system's package manager
- 4. Install the new version, ensuring you select the option to upgrade existing installations if prompted
- 5. Verify the installation was successful by running 'wireshark --version' and confirming it shows 4.6.7
- 6. Test with previously affected pcapng files to confirm the vulnerability is remediated
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-15173 — 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-15173 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