WiresharkApplication
CVE-2026-3203
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 · uneditedRF4CE Profile protocol dissector crash in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 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 RF4CE Profile protocol dissector of Wireshark versions 4.6.0-4.6.3 and 4.4.0-4.4.13. The dissector fails to properly handle malformed or malicious RF4CE packets, causing Wireshark to crash when processing such input, 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.14>= 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 installed Wireshark versionRun 'wireshark --version' or 'tshark --version' to determine the exact version numberAffected if Version is 4.4.0 through 4.4.13, or 4.6.0 through 4.6.3 (not 4.4.14+ or 4.6.4+)
-
Verify RF4CE protocol supportOpen Wireshark, go to Help > About Wireshark > Plugins or check if rf4ce is listed in the supported protocols (packet-rf4ce dissector)Affected if The RF4CE Profile protocol dissector is present and enabled in the installation
-
Identify capture file sourcesReview recent packet capture files opened in Wireshark, especially files from untrusted or unknown sourcesAffected if You have opened or may open pcap/pcapng files containing RF4CE traffic from untrusted sources
You are affected if your Wireshark version falls within 4.4.0-4.4.13 or 4.6.0-4.6.3 AND the RF4CE dissector is enabled and you process capture files that may contain RF4CE traffic.
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.144.6.4
Update Wireshark to version 4.6.4 or later (or the latest 4.4.x version) to obtain the patched dissector. Avoid opening untrusted packet capture files from unknown sources until the update is applied.
Upgrade to Wireshark 4.4.14 (for 4.4.x users) or Wireshark 4.6.4 (for 4.6.x users)
- Identify the currently installed Wireshark version using 'wireshark --version' or 'tshark --version'
- If running Wireshark 4.4.0 through 4.4.13, upgrade to version 4.4.14
- If running Wireshark 4.6.0 through 4.6.3, upgrade to version 4.6.4
- Use the official Wireshark download page (www.wireshark.org) or your system's package manager to obtain the fixed version
- Restart Wireshark or any related tools (tshark, dumpcap) after upgrading
- Verify the new version is installed correctly
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
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3203 — 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-3203 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