WiresharkApplication
CVE-2025-11626
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 · uneditedMONGO dissector infinite loop in Wireshark 4.4.0 to 4.4.9 and 4.2.0 to 4.2.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 confidenceThe MONGO dissector in Wireshark versions 4.4.0 through 4.4.9 and 4.2.0 through 4.2.13 contains an infinite loop vulnerability. When Wireshark processes a specially crafted MongoDB packet that triggers this flaw in the dissector logic, the application enters an infinite loop, causing denial of service through CPU exhaustion and application hang.
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.2.0, < 4.2.14>= 4.4.0, < 4.4.10CVSS 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 installed Wireshark versionRun 'wireshark --version' or check Help > About Wireshark to display the version numberAffected if The version is 4.2.0 through 4.2.13, or 4.4.0 through 4.4.9
-
Confirm MONGO dissector is availableOpen Wireshark and go to Analyze > Enabled Protocols, then search for 'MONGO' in the protocol listAffected if MONGO protocol is enabled in the protocol settings
-
Identify capture files containing MongoDB trafficUse 'tshark -r capture.pcap -Y mongo' or open the capture file and filter by 'mongo' to see if MongoDB traffic is presentAffected if MongoDB protocol packets are present in the capture file being analyzed
-
Check for recent Wireshark crashes or hangsReview system logs or Wireshark crash dumps for any instances of Wireshark becoming unresponsive while processing packet capturesAffected if Wireshark has crashed or hung during analysis of MongoDB traffic
A user is affected if they are running Wireshark versions 4.2.0-4.2.13 or 4.4.0-4.4.9 AND they analyze capture files or live traffic containing MongoDB protocol 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.2.144.4.10
Update Wireshark to version 4.4.10 or later, or 4.2.14 or later, which contain the fix for this vulnerability. Alternatively, avoid opening untrusted packet capture files or limit analysis to trusted network traffic sources.
Wireshark 4.2.14 (for 4.2.x branch) or Wireshark 4.4.10 (for 4.4.x branch)
- 1. Check current Wireshark version via Help > About Wireshark or running 'wireshark --version'
- 2. For Wireshark 4.2.x users: upgrade to Wireshark 4.2.14 or later
- 3. For Wireshark 4.4.x users: upgrade to Wireshark 4.4.10 or later
- 4. Download the appropriate installer from https://www.wireshark.org/download.html
- 5. Install the updated version and restart Wireshark if it was running
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-2025-11626 — 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-2025-11626 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