Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-76926: Denial of Service in Wireshark BUSMASTER File Parser

Published Aug 19, 2026 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS6.5Medium · v3.1
EPSS0.22%13th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-76926CWE-703

CVE-2026-76926 is an improper exceptional-condition handling vulnerability in Wireshark's BUSMASTER capture-file parser, affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18. A newline in an unfinished BUSMASTER header or time statement invokes the Flex scanner's fatal-error handler, which calls exit(2) instead of returning a parse error. The vulnerable call chain runs from wtap_open_offline() through busmaster_open(), run_busmaster_parser(), and busmaster_lex() to yy_fatal_error(). Because the parser participates in automatic capture-format detection, malformed input can terminate Wireshark, TShark, or an application embedding libwiretap without requiring a BUSMASTER file extension.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Processing a crafted capture file terminates the entire host process, interrupting interactive analysis or automated capture-processing services. Applications embedding libwiretap can lose availability when inspecting untrusted input. No code execution, information disclosure, or integrity impact has been demonstrated for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid opening untrusted capture files with affected applications. For automated ingestion, process untrusted captures in isolated worker processes so parser-triggered termination does not terminate a long-lived parent service. Filtering by file extension is insufficient because automatic format detection can invoke the vulnerable parser regardless of the extension.

Remediation

Patch, then assume compromise.

Install vendor-provided Wireshark security updates, including updated libwiretap packages and any bundled copies used by embedding applications. Debian 13 (trixie) provides the fix in version 4.4.18-0+deb13u1. The source-level fix replaces the fatal action for a newline in the HEADER or TIME lexer state with WTAP_ERR_BAD_FILE and a diagnostic, then terminates scanning normally so control returns to the caller. Distribution backports may retain an upstream version number within the affected range; verify the vendor package revision rather than relying solely on the upstream version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Wireshark FoundationWiresharkapplication
FAQ

Frequently asked questions

Is CVE-2026-76926 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-76926 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76926?
Yes. As of Nov 4, 2026, Mallory has reports of a public exploit for CVE-2026-76926.
Is there a patch for CVE-2026-76926?
Install vendor-provided Wireshark security updates, including updated libwiretap packages and any bundled copies used by embedding applications. Debian 13 (trixie) provides the fix in version 4.4.18-0+deb13u1.
What products are affected by CVE-2026-76926?
Wireshark Foundation Wireshark.
How severe is CVE-2026-76926?
CVE-2026-76926 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.22% (13th percentile) as of Nov 4, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.