Threat reportVulnerabilityTL-2026-6552
Wireshark 4.6.10 Released With Patches for 39 Security Advisories (wnpa-sec-2026-111 to -149: dissector, file parser, dissection engine and codec DoS/crash/memory flaws)
Wireshark 4.6.10 (and 4.4.20) fixes 39 security advisories (wnpa-sec-2026-111 through wnpa-sec-2026-149) in protocol dissectors, capture file parsers, the dissection engine and audio codecs. The issues are crashes, infinite loops/hangs and memory leaks, plus an SCTP dissector heap disclosure. Wireshark states it is unaware of any exploits; no public PoC is reported.
Key facts
| Identifiers | TL-2026-6552, CVE-2026-130469, CVE-2026-130468, CVE-2026-130467, CVE-2026-130466, CVE-2026-130465, CVE-2026-130464, CVE-2026-130463, CVE-2026-130462, CVE-2026-130461, CVE-2026-130460, CVE-2026-130459, CVE-2026-130458, CVE-2026-130457, CVE-2026-130456, CVE-2026-130455, CVE-2026-130454, CVE-2026-130453, CVE-2026-130452, CVE-2026-130451, CVE-2026-130450, CVE-2026-130449, CVE-2026-130448, CVE-2026-130447, CVE-2026-130446, CVE-2026-130445, CVE-2026-130444, CVE-2026-130443, CVE-2026-130442, CVE-2026-130441, CVE-2026-130440, CVE-2026-130439, CVE-2026-130438, CVE-2026-130437, CVE-2026-130436, CVE-2026-130435, CVE-2026-130434, CVE-2026-111497 |
|---|---|
| Also known as | wnpa-sec-2026-111 to wnpa-sec-2026-149 |
| Severity | MEDIUM |
| First disclosed | |
| Exploitation status | Linked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-111497 (added ) |
| EPSS | CVE-2026-111497: 82.6% (99.6th percentile); CVE-2026-130461: 0.3% (30.8th percentile); CVE-2026-130468: 0.2% (11.5th percentile) |
| Affected products | Wireshark Foundation Wireshark / TShark; Brotli (bundled in Wireshark Windows and macOS installers) Brotli |
| Malware | Industroyer |
| Tools | TShark, Wireshark, dumpcap |
| MITRE ATT&CK techniques | T1040 Network Sniffing, T1204.002 User Execution: Malicious File, T1499.004 Endpoint Denial of Service: Application or System Exploitation |
| Motivation | UNKNOWN |
| Target sectors | technology, government administration, finance, telecoms, critical-infrastructure |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 10 cited sources |
Detection coverage
As of 2026-11-20, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6552 across Splunk SPL, Microsoft KQL and Sigma, covering 11 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Wireshark/TShark/dumpcap Crash in Dissector or File-Parser Module on Vulnerable Build (wnpa-sec-2026-111 to -149) — Exploitation
Detects Windows Application Error 1000 events for Wireshark.exe, tshark.exe or dumpcap.exe, extracts the faulting module (libwireshark = dissectors/engine, libwiretap = capture file parsers) and flags builds in the vulnerable ranges 4.6.0-4.6.9 and 4.4.0-4.4.19. Dissector and file-parser crashes on malformed packets or crafted capture files (TL-2026-6552, e.g. CVE-2026-130455, CVE-2026-130451, CVE-2026-130462, CVE-2026-130467, CVE-2026-130441) surface as these events. Wireshark reports no known exploitation, so a crash is a symptom to triage (hostile pcap input after user execution of a malicious capture file, or an ordinary bug), not proof of attack.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1499.004, T1499, T1203, T1204.002
- Data sources: wineventlog:WinEventLog:Application, windows_application_event_log
- Severity: medium
- Confidence: medium
Splunk SPL
index=wineventlog sourcetype="WinEventLog:Application" EventCode=1000 (Message="*Faulting application name: Wireshark.exe*" OR Message="*Faulting application name: tshark.exe*" OR Message="*Faulting application name: dumpcap.exe*")
```comment Application Error 1000 for Wireshark family binaries (TL-2026-6552, wnpa-sec-2026-111 to -149)```
| eval faulting_app=lower(mvindex(split(mvindex(split(Message,"Faulting application name: "),1),","),0))
| eval app_version=mvindex(split(mvindex(split(Message,"version: "),1),","),0)
| eval fault_module=lower(mvindex(split(mvindex(split(Message,"Faulting module name: "),1),","),0))
| eval dissector_or_parser_module=if(match(fault_module,"libwireshark|libwiretap|libwsutil"),"yes","no")
| eval vulnerable_build=if(match(app_version,"^4[.]6[.][0-9]([.]0)?$") OR match(app_version,"^4[.]4[.]([0-9]|1[0-9])([.]0)?$"),"yes","no")
| bin _time span=1h
| stats count AS crash_count values(app_version) AS app_version values(fault_module) AS fault_module values(dissector_or_parser_module) AS dissector_or_parser_module values(vulnerable_build) AS vulnerable_build BY _time host faulting_app
| where crash_count>=1
| sort - crash_countMicrosoft KQL
Event
| where TimeGenerated > ago(24h)
| where EventLog == 'Application' and Source == 'Application Error' and EventID == 1000
| where RenderedDescription has_any ('Wireshark.exe', 'tshark.exe', 'dumpcap.exe')
| extend FaultingApp = tolower(extract(@'Faulting application name: ([^, ]+)', 1, RenderedDescription))
| extend AppVersion = extract(@'Faulting application name: [^,]+, version: ([^, ]+)', 1, RenderedDescription)
| extend FaultModule = tolower(extract(@'Faulting module name: ([^, ]+)', 1, RenderedDescription))
| extend DissectorOrParserModule = FaultModule has_any ('libwireshark', 'libwiretap', 'libwsutil')
| extend VulnerableBuild = AppVersion matches regex @'^4[.]6[.][0-9]([.]0)?$' or AppVersion matches regex @'^4[.]4[.]([0-9]|1[0-9])([.]0)?$'
| summarize CrashCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by Computer, FaultingApp, AppVersion, FaultModule, DissectorOrParserModule, VulnerableBuild
| order by CrashCount descSigma
title: Wireshark Family Application Crash (TL-2026-6552)
id: 3f1a7c52-8b4e-4d1a-9c63-1e5a0b7d2f01
status: experimental
description: Detects Application Error 1000 events for Wireshark.exe, tshark.exe or dumpcap.exe, a symptom of dissector or capture file parser crashes fixed in Wireshark 4.6.10 and 4.4.20 (wnpa-sec-2026-111 to -149).
references:
- https://www.wireshark.org/docs/relnotes/wireshark-4.6.10.html
- https://www.wireshark.org/security/wnpa-sec-2026-125
author: Threadlinqs Team
date: 2026-11-20
tags:
- attack.impact
- attack.execution
- attack.t1499.004
- attack.t1499
- attack.t1203
- attack.t1204.002
- cve.2026.130455
- cve.2026.130451
- cve.2026.130462
logsource:
product: windows
service: application
detection:
selection:
Provider_Name: 'Application Error'
EventID: 1000
Data|contains:
- 'Wireshark.exe'
- 'tshark.exe'
- 'dumpcap.exe'
condition: selection
falsepositives:
- Unrelated Wireshark bugs or plugin faults on analyst workstations
- Third-party Npcap or driver issues causing dumpcap faults
level: mediumKnown false positives:
- Ordinary non-malicious Wireshark crashes (plugins, Lua dissectors, GPU/UI issues) on analyst workstations
- Dumpcap faults caused by Npcap driver problems or interface changes
Tuning notes: Treat crashes with vulnerable_build=yes and dissector_or_parser_module=yes as higher priority and correlate with the capture file or interface in use at crash time. Raise the crash_count threshold to 2+ per host per hour in noisy labs. Patched builds (4.6.10 or 4.4.20) that still crash warrant a vendor bug report rather than an incident.
- [indicator]/TShark Opening Capture File From Untrusted Location — User Execution of Hostile Pcap · unlock with TL Creds
- Live Packet Capture via dumpcap/TShark on Non-Analyst Hosts or From Scripting Hosts — Network Sniffing · unlock with TL Creds
- Vulnerable [indicator]/TShark Installed (Defender TVM Inventory) — Patch Exposure for wnpa-sec-2026-111 to -149 · unlock with TL Creds
- [indicator]/TShark Launched From Browser, Mail Client or Archive Tool — Hostile Capture Delivery · unlock with TL Creds
- Npcap/NPF Capture Driver Service Installation — Sniffing Capability Deployed · unlock with TL Creds
- [indicator]/TShark/dumpcap Segmentation Fault in libwireshark/libwiretap on Linux Hosts — Dissector Crash · unlock with TL Creds
- [indicator]/TShark/dumpcap Application Hang (Dissector Infinite Loop) — Post-Exploitation Impact · unlock with TL Creds
- Execution of Vulnerable [indicator]/TShark Build (4.6.0-4.6.9, 4.4.0-4.4.19) — Exposure to Dissector and Parser Flaws · unlock with TL Creds
Indicators of compromise
As of 2026-11-20, Threadlinqs Intelligence tracks 11 indicators of compromise for TL-2026-6552.
Technical analysis
Wireshark 4.6.10 is a security-focused maintenance release. Its release notes list 39 advisories, wnpa-sec-2026-111 through wnpa-sec-2026-149. Thirty-six of them carry CVE IDs in the range CVE-2026-130434 to CVE-2026-130469. Three (wnpa-sec-2026-147 SCTP dissector heap disclosure, wnpa-sec-2026-148 iLBC audio codec crash, wnpa-sec-2026-149 AMR audio codec crash) list no CVE. The count of 39 is therefore a count of advisories, not of CVEs. Advisory pages 125, 147, 148 and 149 are dated November 18, 2026 and state affected versions Wireshark 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19, fixed in 4.6.10 and 4.4.20.
The advisories fall into several groups. Protocol dissector crashes cover RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU (two advisories), ACN, PROFINET, SDP, and MsgPack/NNTP, plus a number of 'multiple protocol dissector crashes' advisories (wnpa-sec-2026-120, 130, 136 to 139, 141, 143, 146). Infinite loops or hangs affect the Kafka dissector (wnpa-sec-2026-125, CVE-2026-130455), multiple dissectors (wnpa-sec-2026-129, CVE-2026-130451) and a mix of dissectors and file parsers (wnpa-sec-2026-118, CVE-2026-130462). Memory leaks affect the TLS dissector (wnpa-sec-2026-131, CVE-2026-130449) and multiple dissectors (wnpa-sec-2026-144, CVE-2026-130436). Capture file parser flaws cover ERF (two crashes), Android Logcat (crash), Ascend and Tektronix K12xx (large loops), and PEAK CAN TRC (crash, only when built with older GLib versions; CVE-2026-130467). One advisory covers a dissection engine crash (wnpa-sec-2026-140, CVE-2026-130441). The grouped advisory wnpa-sec-2026-135 (CVE-2026-130445) combines crashes, infinite loops and leaks.
The release notes attribute the volume to an internal review and a recent trend in AI-assisted vulnerability reports from outside researchers (GitLab issue 21638). Credits on the advisory pages we read include 'Claude and Ada Logics' for the Kafka infinite loop, Khaled Suliman of AISLE Research for the SCTP heap disclosure, YoungJin for the iLBC crash and Simon Huang for the AMR crash. The release also bundles Brotli 1.2.1 in the Windows and macOS installers, which fixes CVE-2026-111497. This is a bundled-component fix, not a Wireshark advisory. Windows installers also move from Npcap 1.88 to 1.89. Prior releases fixed 19 advisories (4.6.9, wnpa-sec-2026-92 to -110) and 28 (4.6.8) according to the coverage.
From the advisory titles, the practical risk is availability. A malformed packet on the wire or a crafted trace file could crash or hang Wireshark/TShark and tooling built on its dissectors, such as analyst workstations, automated pcap triage and sensor pipelines; the Kafka advisory describes excessive CPU use. The SCTP advisory describes heap memory disclosure and notes that a malformed packet or trace file could expose Wireshark to additional issues. The sources give no CVSS scores, no CWE IDs, no exploitation reports ('We are unaware of any exploits for this issue'), no PoC and no network IOCs, so no BeaconBeagle correlation applies. Defenders should upgrade to 4.6.10 (or 4.4.20 on the older branch) and treat untrusted pcap files as hostile input.
MITRE ATT&CK techniques by tactic:
Credential Access
Discovery
Execution
T1204.002 User Execution: Malicious File
Impact
T1499.004 Endpoint Denial of Service: Application or System Exploitation
Remediation
Patches
- Wireshark 4.6.10 and Wireshark 4.4.20
- Windows and macOS installers bundle Brotli 1.2.1 (fixes CVE-2026-111497)
- Windows installers ship Npcap 1.89 (previously 1.88)
Immediate actions
- Upgrade Wireshark/TShark to 4.6.10 (or 4.4.20 on the 4.4 branch) on analyst workstations, sensors and automated pcap-processing hosts
- Do not open capture files from untrusted sources in an unpatched Wireshark
- Run pcap triage pipelines in isolated, resource-limited environments with timeouts
Workarounds
- Disable unneeded protocol dissectors via Enabled Protocols where upgrade is not immediately possible (general Wireshark control; the SCTP guidance comes from the earlier wnpa-sec-2026-93 advisory, not this release)
Longer-term hardening
- Add Wireshark/TShark/dumpcap to software inventory and patch SLAs
- Monitor for repeated Wireshark/TShark crashes or hangs during pcap processing
- Restrict who can feed untrusted captures into automated TShark workflows
Affected and fixed versions
- Wireshark Foundation — Wireshark / TShark
Vulnerable versions: 4.6.0 to 4.6.9; 4.4.0 to 4.4.19
Fixed in: 4.6.10; 4.4.20 - Brotli (bundled in Wireshark Windows and macOS installers) — Brotli
Vulnerable versions: Versions prior to 1.2.1 as bundled (CVE-2026-111497)
Fixed in: 1.2.1
Timeline
- Release notes attribute the large number of fixes to an internal review and a recent trend of AI-assisted vulnerability reports from outside researchers (issue 21638).
- Release notes: Windows and macOS installers ship Brotli 1.2.1 (fixes CVE-2026-111497); Windows installers update Npcap from 1.88 to 1.89. Date is that of the advisory pages; the notes are undated.
- wnpa-sec-2026-148 (iLBC, credited to YoungJin) and -149 (AMR, credited to Simon Huang) describe codec crashes on malformed packets or trace files; no CVE IDs listed.
- wnpa-sec-2026-147: SCTP dissector heap disclosure (issue 21712), credited to Khaled Suliman of AISLE Research; no CVE listed and Wireshark is unaware of any exploits.
- wnpa-sec-2026-125 (CVE-2026-130455): Kafka dissector infinite loop; a malformed packet or trace file can cause excessive CPU use. Credited to Claude and Ada Logics (issue 21684).
- Fixed in Wireshark 4.6.10 and 4.4.20; affected versions are 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19. The release notes themselves carry no date.
- Wireshark advisory pages for wnpa-sec-2026-125 (Kafka), -147 (SCTP), -148 (iLBC) and -149 (AMR) are dated November 18, 2026; the index marks advisories 111 to 149 as fixed in 4.6.10.
- Cyber Security News reports Wireshark 4.6.10 with patches for 39 advisories, noting not all have CVEs, and cites earlier releases 4.6.9 (19 advisories) and 4.6.8 (28).
Sources cited
- Wireshark Security Advisories index wireshark.org · Advisory
- wnpa-sec-2026-147: SCTP protocol dissector heap disclosure wireshark.org · Advisory · 2026-11-18
- wnpa-sec-2026-125: Kafka protocol dissector infinite loop (CVE-2026-130455) wireshark.org · Advisory · 2026-11-18
- wnpa-sec-2026-148: iLBC audio codec crash wireshark.org · Advisory · 2026-11-18
- wnpa-sec-2026-149: AMR audio codec crash wireshark.org · Advisory · 2026-11-18
- CVE-2026-111497 (Brotli, fixed by bundled 1.2.1) CVE Program · Advisory
- Wireshark 4.6.10 Release Notes wireshark.org · Vendor report
- Wireshark 4.6.9 Release Notes (prior release, includes wnpa-sec-2026-93 SCTP crash) wireshark.org · Vendor report
- Wireshark issue 21638: AI-assisted vulnerability reports GitLab · Code repository
- Wireshark 4.6.10 Released With Patch for 39 Security Vulnerabilities (Cyber Security News) cybersecuritynews.com · News · 2026-11-20
Previous and next in vulnerability
- Telegram Widgets Sandbox Escape: Claimed RCE Chains Bypassing Telegram for Android 13.2.2 Widget Hardening (QuickJS-ng Use-After-Return) and Suspected WebRAT/Salat Stealer Delivery Previous report
- Unsupported Windows and Actively Exploited (CISA KEV) Vulnerabilities in Small Business IT: ~196,000 SMB Machines Lose All Patch Coverage on October 13, 2026 Next report
Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated —.