Skip to content
Networks

CVE-2026-76886

8.1
High
EPSS 0.32%Patch availableAug 21, 2026

C12.22 protocol dissector crash allows remote denial-of-service.

common questions

Is CVE-2026-76886 being exploited?

Not confirmed. CVE-2026-76886 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-76886?

CVE-2026-76886 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76886?

Yes. A fix has been recorded for CVE-2026-76886. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76886 affect?

CVE-2026-76886 affects C12.22 protocol implementations, network analyzers/packet parsers, smart meter gateways, protocol libraries. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76886?

Apply vendor fixes when available; block/inspect C12.22 traffic and update IDS signatures.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
C12.22 protocol implementationsnetwork analyzers/packet parserssmart meter gatewaysprotocol libraries
impact

Remote denial of service via crafted C12.22 packets that crash the protocol dissector (heap overflow), disrupting packet parsers, gateways, or metering devices.

action required

Patch when possible

affected versions
Wireshark Foundation Wireshark
  • affected>= 4.6.0 and < 4.6.8
  • affected>= 4.4.0 and < 4.4.18

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free