Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-6868: Stack-Based Buffer Overflow in Wireshark HTTP Dissector

Published Apr 30, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-6868CWE-121 · Stack-based Buffer Overflow

CVE-2026-6868 is a stack-based buffer overflow/read flaw in Wireshark's HTTP protocol dissector. When packets reach the HTTP dissector through an X.25 conversation path rather than the normal TCP path, the dissector can treat stale or uninitialized stack memory as TCP metadata and read beyond a stack buffer boundary. The resulting crash can be triggered while processing malformed network traffic or a malformed packet-capture file. Affected releases are Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14.

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.

Successful exploitation causes Wireshark or TShark to crash, resulting in denial of service. No confidentiality or integrity impact is established by the available information.

Mitigation

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

Until upgraded, avoid analyzing untrusted packet-capture files and limit exposure of live-capture or analysis systems to untrusted network traffic. Restrict who can inject traffic into monitored network segments where feasible.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.6.5 or later on the 4.6 release branch, or to version 4.4.15 or later on the 4.4 release branch.

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-6868 exploited in the wild?
As of Oct 1, 2026, Mallory has no reports of CVE-2026-6868 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6868?
Yes. As of Oct 1, 2026, Mallory has reports of a public exploit for CVE-2026-6868.
Is there a patch for CVE-2026-6868?
Upgrade Wireshark to version 4.6.5 or later on the 4.6 release branch, or to version 4.4.15 or later on the 4.4 release branch.
What products are affected by CVE-2026-6868?
Wireshark Foundation Wireshark.
How severe is CVE-2026-6868?
CVE-2026-6868 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.19% (9th percentile) as of Oct 1, 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.