Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-76885: Heap Out-of-Bounds Read in Wireshark Tektronix K12xx 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.21%12th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-76885CWE-125

CVE-2026-76885 is a heap out-of-bounds read in Wireshark's Tektronix K12xx capture-file parser, affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18. The get_record() function includes skipped 16-byte blobs in its returned byte count even though those bytes are not copied into the record buffer. The k12_read() and k12_seek_read() functions propagate this inflated length to process_packet_data(), which can read beyond the heap allocation when copying extra information through ws_buffer_append() and memcpy(). A crafted record crossing a blob boundary can trigger a parser crash and denial of service. The defect was also reproduced in a 4.7.2 development build using TShark and Capinfos.

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 malicious Tektronix K12xx capture can crash the affected Wireshark application or command-line utility, interrupting capture-file analysis. A demonstrated case read 16 bytes beyond an 8192-byte heap allocation. The established security impact is denial of service; confidentiality loss, integrity compromise, and arbitrary-code execution are not established for this CVE.

Mitigation

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

Until patched, avoid opening or automatically processing untrusted Tektronix K12xx captures with affected Wireshark utilities. Restrict capture-file submissions to trusted sources and isolate capture-processing workloads to limit disruption from parser crashes.

Remediation

Patch, then assume compromise.

Install a vendor-supported Wireshark update containing the K12 buffer-overrun fix, including corresponding updates to capture-file libraries and command-line utilities. For upstream releases, use a fixed release beyond the affected 4.6.0–4.6.7 or 4.4.0–4.4.18 ranges. Debian 13 provides the backported fix in version 4.4.18-0+deb13u1. Distribution package versions must be evaluated against their security advisories because backported fixes may retain an otherwise affected upstream version number.

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-76885 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-76885 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76885?
Yes. As of Nov 4, 2026, Mallory has reports of a public exploit for CVE-2026-76885.
Is there a patch for CVE-2026-76885?
Install a vendor-supported Wireshark update containing the K12 buffer-overrun fix, including corresponding updates to capture-file libraries and command-line utilities. For upstream releases, use a fixed release beyond the affected 4.6.0–4.6.7 or 4.4.0–4.4.18 ranges.
What products are affected by CVE-2026-76885?
Wireshark Foundation Wireshark.
How severe is CVE-2026-76885?
CVE-2026-76885 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.21% (12th 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.