Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Wireshark 4.6.10 and 4.4.20 Address Dozens of Packet-Parser Security Issues

Wireshark's November 18 maintenance updates include 39 security advisories for its 4.6 branch involving protocol dissectors, file parsers, hangs and memory issues. Update before processing untrusted captures.

Newsroom editorial artwork
PUBLISHED

IPCRIME | November 20, 2026. The Wireshark project has released 4.6.10 and 4.4.20, security-focused updates for the widely used network-protocol analyzer. The announcement was published November 18 and includes an unusually broad set of corrections after an internal review and a wave of outside vulnerability reports, some produced with AI-assisted techniques.

The Wireshark 4.6.10 release notes enumerate 39 security advisories, wnpa-sec-2026-111 through wnpa-sec-2026-149. They include a mixture of crashes, parsing loops, memory leaks and other flaws in protocol dissectors and capture-file readers. A count of advisories is not a count of confirmed remote code-execution attacks, and it is not evidence that every CVE affects every installation equally.

Why a network-analysis program needs security patches

Wireshark regularly opens material an analyst did not create: packet captures supplied by a customer, traffic recorded near a compromised system, unusual industrial protocols or files acquired during an incident. These files can contain deliberately malformed structures. Software that attempts to interpret every byte must handle lengths, nesting and malformed input safely, or reading the evidence can become an attack surface.

The published advisories include examples such as RTSE and NBAP dissector crashes, several ERF and other capture-file parser problems, Kafka dissection loops, a TLS dissector memory leak, an SCTP heap-disclosure issue and additional crashes in codecs and other dissectors. Their severity and exploit prerequisites vary. IPCRIME is not labeling all of them as exploitable by an Internet attacker, because some require an analyst to open a malicious capture.

Specific version and packaging details

Wireshark’s official announcement confirms 4.6.10 and 4.4.20 as the corresponding maintenance releases. Analysts should check the version their system or repository actually ships, rather than assuming that a package manager’s general ‘up to date’ status implies it contains the upstream fixes. In addition to Wireshark’s own code, official Windows and macOS installers now include an updated Brotli library; the 4.6.10 Windows package also updates Npcap.

Linux distributions can ship backported fixes under release numbers that differ from upstream. Confirm through the distribution’s security notices and package changelogs before treating a different number as automatically unpatched.

An evidence-safe workflow

  • Record the installed Wireshark version and distribution package before processing untrusted files.
  • Obtain supported maintenance updates from official sources or a trusted operating-system repository.
  • Preserve the original packet-capture file, its hash and provenance. Analyze a working copy in a controlled environment.
  • Restrict elevated privileges; routine packet analysis should not require every parsing process to run as administrator or root.
  • Treat extracted data from captures as potentially sensitive, including authentication material, internal network names and personal information.

Risk and evidence limits

Wireshark’s release note lists the security corrections but does not establish a public exploitation campaign involving these particular disclosures. A malformed traffic sample that crashes a local parser is different from a network service allowing unauthenticated remote execution. For any specific CVE, use the relevant advisory to determine what interaction is required.

The new Wireshark maintenance releases are also a useful reminder that forensic and defensive tools themselves require careful patching. A trusted tool is not a trusted version forever.

Official release documentation

Wireshark — November 18 release announcement; Wireshark Foundation mailing-list release notes, security advisories 111–149; Official Wireshark download and verification resources.

Research-based security summary; IPCRIME has not reproduced the parser flaws or independently benchmarked the released binaries.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.

2 responses to “Wireshark 4.6.10 and 4.4.20 Address Dozens of Packet-Parser Security Issues”