Loading vulnerability…
CVE-2026-6868 is a stack-based buffer overflow in Wireshark's HTTP protocol dissector affecting Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. The flaw occurs in dissect_http_tcp() in packet-http.c when the HTTP dissector is reached through an X.25 conversation path rather than the normal TCP path. In that scenario, the data argument is treated as though it were a valid tcpinfo structure and tcpinfo->flags is read, but the pointer can instead reference stale or uninitialized stack memory. This results in a 2-byte out-of-bounds stack read and can crash Wireshark or TShark while dissecting malformed traffic or crafted capture data.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced as part of the Wireshark 4.6.8 advisory/plugin CVE list, but not described individually in the content.
A Wireshark HTTP dissector vulnerability that can cause an application crash when processing malformed traffic.
A stack-based buffer overflow in Wireshark's HTTP protocol dissector that can cause a denial of service.
A denial-of-service vulnerability in Wireshark's HTTP protocol dissector that can cause the application to crash when processing malformed network packets or malformed packet trace files.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.