CVE-2026-76886

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-20) is not newer than that change (2026-10-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-63142 (ENISA EUVD) · GHSA-wrhv-64xq-9g54 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (GitLab Inc.) states them: "Upgrade to version 4.6.8 or above".

C12.22 protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Oct 26, 2026
Patch available.
Web page

CMS MessageDigest verification dereferences missing algorithm (#21446) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/work_items/21446
Web page

Wireshark • Go Deep | Wireshark • wnpa-sec-2026-75 C12.22 protocol dissector crash

https://www.wireshark.org/security/wnpa-sec-2026-75.html
Web page

EAX CMAC 16-bit length truncation can overflow heap on large C12.22 cleartext-auth payloads (#21439) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/work_items/21439

Vendor Advisories for CVE-2026-76886(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatwireshark-1:4.4.2-10.el10_2.82026-10-19redhat
redhatwireshark-1:2.6.2-21.el8_102026-10-15redhat
redhatwireshark-1:3.4.10-9.el9_8.52026-10-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.0.10-1 ... 4.6.6-2 (50 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.4.13-0+deb13u1 ... 4.4.9-1 (7 versions)
  • every version up to 4.4.18-0+deb13u1: fixed in 4.4.18-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.4.7-1 ... 4.6.6-2 (16 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 128× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 415 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 315 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 20:57 UTCEG score recompute
  2. 2026-11-01 20:57 UTCVendor advisory
  3. 2026-11-01 20:57 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-31 22:56 UTCEG score recompute
  6. 2026-10-31 22:56 UTCVendor advisory
  7. 2026-10-31 22:56 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-31 00:56 UTCEG score recompute
  10. 2026-10-31 00:56 UTCVendor advisory
  11. 2026-10-31 00:56 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-30 02:56 UTCEG score recompute
  14. 2026-10-30 02:56 UTCVendor advisory
  15. 2026-10-30 02:56 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-29 04:55 UTCEG score recompute
  18. 2026-10-29 04:55 UTCVendor advisory
  19. 2026-10-29 04:55 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-28 06:55 UTCEG score recompute
  22. 2026-10-28 06:55 UTCVendor advisory
  23. 2026-10-28 06:55 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-27 08:54 UTCEG score recompute
Show 75 more
  1. 2026-10-27 08:54 UTCVendor advisory
  2. 2026-10-27 08:54 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-26 09:28 UTCEG score recompute
  5. 2026-10-26 09:28 UTCVendor advisory
  6. 2026-10-26 09:28 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-25 14:01 UTCEG score recompute
  9. 2026-10-25 11:28 UTCEG score recompute
  10. 2026-10-25 11:28 UTCVendor advisory
  11. 2026-10-25 11:28 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-24 13:27 UTCEG score recompute
  14. 2026-10-24 13:27 UTCVendor advisory
  15. 2026-10-24 13:27 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-23 23:27 UTCEG score recompute
  17. 2026-10-23 23:27 UTCVendor advisory
  18. 2026-10-23 23:27 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-23 21:25 UTCEG score recompute
  20. 2026-10-23 21:25 UTCVendor advisory
  21. 2026-10-23 21:25 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-22 23:24 UTCEG score recompute
  24. 2026-10-22 23:24 UTCVendor advisory
  25. 2026-10-22 23:24 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  26. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-10-22 01:24 UTCEG score recompute
  28. 2026-10-22 01:24 UTCVendor advisory
  29. 2026-10-22 01:24 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  30. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-10-21 03:22 UTCEG score recompute
  32. 2026-10-21 03:22 UTCVendor advisory
  33. 2026-10-21 03:21 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  35. 2026-10-20 05:20 UTCEG score recompute
  36. 2026-10-20 05:20 UTCVendor advisory
  37. 2026-10-20 05:20 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  38. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  39. 2026-10-19 06:39 UTCEG score recompute
  40. 2026-10-19 06:39 UTCVendor advisory
  41. 2026-10-19 06:39 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  42. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  43. 2026-10-18 08:36 UTCVendor advisory
  44. 2026-10-18 08:36 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-10-18 03:12 UTCEG score recompute
  46. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  47. 2026-10-17 10:00 UTCEG score recompute
  48. 2026-10-17 10:00 UTCVendor advisory
  49. 2026-10-17 10:00 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  51. 2026-10-16 11:58 UTCEG score recompute
  52. 2026-10-16 11:58 UTCVendor advisory
  53. 2026-10-16 11:57 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  55. 2026-10-15 13:11 UTCEG score recompute
  56. 2026-10-15 13:10 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-10-14 08:18 UTCEG score recompute
  59. 2026-10-14 08:18 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  60. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  61. 2026-10-13 03:32 UTCEG score recompute
  62. 2026-10-13 03:32 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  64. 2026-10-12 15:38 UTCEG score recompute
  65. 2026-10-12 05:30 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-10-11 19:23 UTCEG score recompute
  67. 2026-10-11 16:39 UTCEG score recompute
  68. 2026-10-11 13:58 UTCEG score recompute
  69. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  70. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  73. 2026-10-08 09:57 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1
  74. 2026-10-08 05:56 UTCEG score recompute
  75. 2026-10-08 05:56 UTCGHSA enrichmentGHSA-wrhv-64xq-9g54 · GitHub severity HIGH · GitHub CVSS 8.1

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-76886?
CVE-2026-76886 is a critical-severity vulnerability; its CVE record was published on August 19, 2026. C12.22 protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service
When was the CVE record for CVE-2026-76886 published?
The CVE record for CVE-2026-76886 was published on August 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-76886 actively exploited?
CVE-2026-76886 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76886?
CVE-2026-76886 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-76886?
A fix for CVE-2026-76886 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (GitLab Inc.) states them: "Upgrade to version 4.6.8 or above". The vendor advisories EchelonGraph has for CVE-2026-76886 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76886

Explore →

Is Your Infrastructure Affected by CVE-2026-76886?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs