Wireshark patched nearly 40 vulnerabilities. It blames AI for the flood.
The Wireshark Foundation released 4.6.10 on November 18, 2026, with a security fix count that makes most releases look lazy. Nearly 40 flaws went in at once. That is a lot for a packet analyzer most people treat as background software.
The notes were refreshingly blunt about the cause. As the project put it, the spike came partly from "a recent trend in AI-assisted vulnerability reports from outside researchers." The bots found the bugs. The humans still closed them.
Nearly 40, spread thin
Rather than one dramatic hole, the fixes crawl across dozens of dissectors and parsers. Most follow the same script: hand the analyzer a crafted packet or a bad capture file, and it crashes. Not fatal. Just annoying.
The advisories run from wnpa-sec-2026-111 through wnpa-sec-2026-149, and most carry a CVE-2026-1304xx number. You will find crashes in the RTSE, NBAP, and PROFINET dissectors. The ERF and Android Logcat parsers bite on malformed files. The Ascend parser and Kafka spun up loops that just kept churning.
Two are worth paying attention to. A numeric truncation in the LoRaWAN decryption path could allow remote code execution, and it was coordinated with the Zero Day Initiative under the tag ZDI-CAN-32851. That is a real one.
For the record, though, most of the 40 carry the same disclaimer: no known exploits, and the impact is a crash. Wireshark is unaware of anyone actually weaponizing these. Treat the RCE items as the exception, not the rule.
This wave predates the release
Forty at once looks shocking until you recall that Wireshark 4.6.5 already patched 43 vulnerabilities a while back. Didier Stevens of SANS flagged AI as the driver then too, so this is a trend, not an anomaly.
The numbers behind it are uglier still. VulnCheck says its "Report a Vulnerability" service jumped 10-fold in a single year, with 51% of reporters crediting AI with the finds. CVEs climbed roughly 100% year over year. Exploits move faster now: the median time from publication to a KEV listing fell from 120 days in 2025 to about 80 days in the first half of 2026.
Big companies absorb this better. Microsoft and Google have dedicated security teams. Wireshark runs on volunteers, which is why the project ran its own internal review alongside the outside reports. Validate the payload before trusting anything a script hands you.
The industry is trying to adapt, unevenly. Linus Torvalds wrote in May 2026 that the kernel security mailing list had become nearly unmanageable, choked with duplicates from people finding the same bugs with the same tools. His advice was blunt: read the docs, submit a patch too, and add value beyond what the AI did. GitHub now wants a working proof of concept for AI-assisted finds. cURL removed its bounties to starve the slop, and Daniel Stenberg noticed that volume and quality of reports went up, which is a twist he did not seem to want.
Upgrade, then go back to work
The advice here is boring and correct. Install 4.6.10, or 4.4.20 if you are still on the older branch. Keep in mind that many flaws trigger when you open a capture from an untrusted source or view crafted traffic. Do either regularly, and updating actually matters.
A few details worth knowing. The Windows installers now ship with brotli 1.2.1, which closes a separate CVE, plus Npcap 1.89. On Unix systems, extcap helpers now live under a libexec directory by default, overridable through the WIRESHARK_EXTCAP_DIR environment variable. No action required unless you script your own setup.
There is also no new protocol support here. This is a maintenance release about stability, not flash. If you were banking on a new dissector, you will have to wait.
The tool behind the numbers
One thing worth pausing on. Wireshark started in 1998 as Ethereal, built by Gerald Combs at a small ISP. Commercial analyzers ran around $1,500 then and would not run on Linux, so he made his own. He renamed it in 2006 because he did not own the trademark. The project now claims over 2,000 contributors and 60 million downloads over five years, and it moved under the nonprofit foundation in 2023 after a stop at Riverbed and Sysdig.
That lineage is the irony. An open, volunteer-built tool that became an industry standard is now the one strained by machine-generated bug reports. The same model that built it is being tested by the flood.
Head here to the downloads
