Skip to main content
Mallory
HighVulnerability

CVE-2026-76880: Denial of Service in Wireshark RRC Protocol Dissector

Published Aug 19, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days20 mentions · peak 5 in a dayToday
CVSS7.5High · v3.1
EPSS0.24%16th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-76880CWE-787 · Out-of-bounds Write

CVE-2026-76880 is an out-of-bounds write vulnerability in Wireshark's RRC protocol dissector affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18. Processing specially crafted RRC protocol data can cause the dissector to crash, resulting in denial of service. The exact vulnerable function and triggering input fields are not specified.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the affected Wireshark process and interrupt packet inspection or analysis. The vulnerability-specific assessment identifies high availability impact without confidentiality or integrity impact. Arbitrary code execution and information disclosure are not established for this CVE.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid processing untrusted UMTS RRC traffic or capture files that could invoke the affected dissector. This reduces exposure but does not correct the underlying out-of-bounds write.

Remediation

Patch, then assume compromise.

Install the applicable vendor security update or upgrade to a release confirmed to address CVE-2026-76880. For Debian stable (trixie), the designated fixed package is 4.4.18-0+deb13u1. For RHEL 10.2, RHSA-2026:84721 supplies fixed packages with version-release 4.4.2-10.el10_2.8. Distribution packages may contain backported fixes despite retaining an otherwise affected upstream version number.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Wireshark FoundationWiresharkapplication
FAQ

Frequently asked questions

Is CVE-2026-76880 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-76880 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76880?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-76880.
Is there a patch for CVE-2026-76880?
Install the applicable vendor security update or upgrade to a release confirmed to address CVE-2026-76880. For Debian stable (trixie), the designated fixed package is 4.4.18-0+deb13u1.
What products are affected by CVE-2026-76880?
Wireshark Foundation Wireshark.
How severe is CVE-2026-76880?
CVE-2026-76880 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.24% (16th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+34 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.