UMTS FP protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service
CVE-2026-76889
Score 4.7 from GitHub Security Advisory published 2026-08-20. a secondary CVSS source baseline 4.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(high)
- EG Risk
- 21(Track)EG Risk 21/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity47% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026UMTS FP MAC-is descriptor count causes fixed-array out-of-bounds writes (#21413) · Issues · Wireshark Foundation / Wireshark · GitLab
https://gitlab.com/wireshark/wireshark/-/work_items/21413Wireshark • Go Deep | Wireshark • wnpa-sec-2026-66 UMTS FP protocol dissector crash
https://www.wireshark.org/security/wnpa-sec-2026-66.htmlVendor Advisories for CVE-2026-76889(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:34 UTCEG score recompute
- 2026-08-20 16:34 UTCGHSA enrichment
- 2026-08-20 15:45 UTCEG score recompute
- 2026-08-20 15:45 UTCGHSA enrichment
- 2026-08-19 23:20 UTCEG score recompute
- 2026-08-19 22:43 UTCEG score recompute
- 2026-08-19 22:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
- CVE-2016-9603NVD 5.5EG 9.9EPSS p91CRITICAL
- CVE-2017-20241EG 9.8CRITICAL
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2019-18296EG 9.8EPSS p91CRITICAL
- CVE-2019-18295EG 9.8EPSS p91CRITICAL
- CVE-2019-18293EG 9.8EPSS p91CRITICAL
- CVE-2019-18289EG 9.8EPSS p91CRITICAL
- CVE-2019-14901EG 9.8EPSS p97CRITICAL
- CVE-2019-14895EG 9.8EPSS p94CRITICAL
Frequently asked(5)
What is CVE-2026-76889?
When was CVE-2026-76889 disclosed?
Is CVE-2026-76889 actively exploited?
What is the CVSS score of CVE-2026-76889?
How do I remediate CVE-2026-76889?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76889
Is Your Infrastructure Affected by CVE-2026-76889?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.