CVE-2026-6870

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-30. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GSM RP protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
41(Track)
EG Risk 41/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 computed
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.6%
KEV
Not listed

Published

April 30, 2026

Last Modified

May 1, 2026

Advisory Details (2)

Auto-updated May 1, 2026
No patch confirmed yet.
generic

stale g_tree in packet-gsm_a_rp.c when RP User-Data is dissected via BSSMAP VGCS-SMS leads to heap overflow read (crash/oob) (#21189) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/work_items/21189
generic

Wireshark • Go Deep | Wireshark • wnpa-sec-2026-43 GSM RP protocol dissector crash

https://www.wireshark.org/security/wnpa-sec-2026-43.html

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 42× 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.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:22 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 20:18 UTCOSV refresh
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 68 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:50 UTCEPSS rescore
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-19 19:26 UTCEPSS rescore
  25. 2026-06-19 19:26 UTCEPSS rescore
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-18 17:52 UTCEPSS rescore
  28. 2026-06-16 17:53 UTCEPSS rescore
  29. 2026-06-15 17:49 UTCEPSS rescore
  30. 2026-06-15 17:49 UTCEPSS rescore
  31. 2026-06-14 23:18 UTCEPSS rescore
  32. 2026-06-14 09:19 UTCGHSA enrichment
  33. 2026-06-13 23:00 UTCEPSS rescore
  34. 2026-06-12 23:12 UTCEPSS rescore
  35. 2026-06-12 23:12 UTCEPSS rescore
  36. 2026-06-12 10:28 UTCGHSA enrichment
  37. 2026-06-11 14:00 UTCEPSS rescore
  38. 2026-06-11 09:39 UTCGHSA enrichment
  39. 2026-06-10 22:19 UTCEPSS rescore
  40. 2026-06-10 13:22 UTCEPSS rescore
  41. 2026-06-10 09:28 UTCGHSA enrichment
  42. 2026-06-09 09:40 UTCGHSA enrichment
  43. 2026-06-08 09:27 UTCGHSA enrichment
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 09:40 UTCGHSA enrichment
  46. 2026-06-06 13:47 UTCEPSS rescore
  47. 2026-06-06 09:50 UTCGHSA enrichment
  48. 2026-06-05 10:02 UTCGHSA enrichment
  49. 2026-06-05 06:10 UTCEPSS rescore
  50. 2026-06-04 13:12 UTCEPSS rescore
  51. 2026-06-04 10:15 UTCGHSA enrichment
  52. 2026-06-03 10:27 UTCGHSA enrichment
  53. 2026-06-02 20:13 UTCEPSS rescore
  54. 2026-06-02 10:40 UTCGHSA enrichment
  55. 2026-06-01 13:52 UTCEPSS rescore
  56. 2026-06-01 10:42 UTCGHSA enrichment
  57. 2026-05-31 00:16 UTCEPSS rescore
  58. 2026-05-31 00:16 UTCEPSS rescore
  59. 2026-05-29 13:44 UTCEPSS rescore
  60. 2026-05-29 13:44 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-26 13:44 UTCEPSS rescore
  64. 2026-05-21 22:43 UTCEPSS rescore
  65. 2026-05-20 22:38 UTCEPSS rescore
  66. 2026-05-20 15:04 UTCEG score recompute
  67. 2026-05-20 15:04 UTCGHSA enrichment
  68. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6870?
CVE-2026-6870 is a medium vulnerability published on April 30, 2026. GSM RP protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service
When was CVE-2026-6870 disclosed?
CVE-2026-6870 was first published in the National Vulnerability Database on April 30, 2026, with the most recent update on May 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6870 actively exploited?
CVE-2026-6870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6870?
CVE-2026-6870 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-6870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6870, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6870

Explore →

Is Your Infrastructure Affected by CVE-2026-6870?

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

Start Free Scan →Browse All CVEs