CVE-2026-6870 is an out-of-bounds read and crash vulnerability in Wireshark and TShark's GSM RP protocol dissector. A stale global tree state in the GSM RP dissector can be used after its valid lifetime when RP User-Data is dissected through the BSSMAP VGCS-SMS path. Processing a stateful malformed packet sequence can cause a heap-buffer-overflow read and terminate the application. Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14 are affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability listed as addressed by the Rocky Linux 9.6 TuxCare security advisory; no technical flaw details are provided.
A vulnerability included in the referenced AlmaLinux advisory; no technical details are provided.
A Wireshark vulnerability referenced by the plugin; no individual technical details are provided.
A Wireshark vulnerability referenced by the plugin; no specific technical details are provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.