In 30 seconds
A security researcher says three bugs they reported have just gone public through the Zero Day Initiative, the vulnerability broker known as ZDI, which coordinates disclosure between researchers and vendors. Two of them hit Wireshark, the widely used tool for inspecting network traffic: ZDI-26-899, an integer overflow in the LBMC dissector, and ZDI-26-898, a numeric truncation bug in the LoRaWAN dissector. Both carry the RCE label, short for remote code execution, the most serious class of flaw. Everything so far comes from the researcher's own announcement, so treat the specifics as claimed rather than independently confirmed.heegong123x.com · heegong123 · xOpen original sourceSee in source list
What happened
On X, a researcher posting as heegong123 announced that three vulnerabilities they had reported are now publicly disclosed through ZDI, and thanked the ZDI team for coordinating the process. The list includes the two Wireshark flaws plus a third item, ZDI-26-868, described as a denial of service in Windows Aero Theme handling. Public disclosure here means the advisory IDs are out in the open for anyone to read.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Why it matters
Wireshark is the tool engineers reach for when something on a network looks wrong, and dissectors are its parser modules, the code that decodes each protocol's packets. If a malformed packet or capture file can trigger memory corruption, as the integer overflow and truncation labels suggest, the machine doing the analysis becomes the target instead of the shield. An analyst opening a booby-trapped capture is the classic scenario for this bug class. That said, the severity picture rests on one short announcement, and the precise preconditions, such as affected versions and required user interaction, are not visible yet.heegong123x.com · heegong123 · xOpen original sourceSee in source list
What to do
The practical move is to look up advisories ZDI-26-899 and ZDI-26-898 on the ZDI site for affected versions and mitigation notes, then update Wireshark as soon as a fixed release is available. Until then, treat capture files and packet traces from unfamiliar sources with the same caution as untrusted documents. Teams whose analysts routinely open customer-supplied captures have the strongest reason to check their versions now.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Confirmed and still uncertain
What is established in the current evidence is narrow: a public announcement listing three advisory IDs with one-line descriptions. What is not known includes whether a patched Wireshark release already exists, whether any exploitation has been seen in the wild, the affected version ranges, the discovery dates, and how long ZDI spent coordinating with the vendor. The identity behind the handle heegong123 is also unverified here, and the RCE labels may reflect either demonstrated code execution or an assessment that it is reachable.heegong123x.com · heegong123 · xOpen original sourceSee in source list
What people are saying
The only voice in the evidence so far is the researcher's own. Heegong123 framed the news as a milestone, noting that three more of their reported vulnerabilities have now been disclosed, and closed with thanks to the ZDI team for coordinating. No statement from the Wireshark project, from ZDI itself, or from any vendor appears in this batch.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Evolution
The visible timeline has a single data point: the announcement post stating that the bugs were reported by the researcher and are now disclosed. That brackets a private phase, the reporting and coordination work, which the current evidence does not expose.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Reconstructing the usual arc, a researcher reports to ZDI, ZDI works with the vendor toward a patch, and details go public at disclosure. Whether these Wireshark flaws followed that arc exactly, and whether a patch shipped before or alongside the disclosure, cannot be determined from this batch.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Reach
1 independent groups, 1 updates, and 0 engagements.
Technical detail
According to the announcement, ZDI-26-899 is an integer overflow in the LBMC dissector, meaning a value grows beyond what its storage type can hold, a classic route to memory corruption. ZDI-26-898 is described as numeric truncation in the LoRaWAN dissector, the parser for the long-range, low-power protocol used by IoT devices, where a value loses fidelity when squeezed into a smaller type. Both are labeled RCE, remote code execution. The one-line descriptions do not specify affected versions, exploit preconditions, or whether code execution was demonstrated or only assessed as reachable.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Sources and evidence
This story currently rests on a single source: one X post by heegong123, the person claiming credit for reporting the bugs. It is a primary account in the sense that it comes straight from the reporter, but it is also self-reported, and the batch includes no ZDI advisory text, vendor changelog, or patch reference to corroborate the specifics. Confidence in the details rises or falls once the advisories themselves surface.heegong123x.com · heegong123 · xOpen original sourceSee in source list
Sources
- heegong123x.com · heegong123 · x



