CVE-2026-5405

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

RDP protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service and possible code execution

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 1, 2026

Last Modified

July 15, 2026

Advisory Details (2)

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

Wireshark • Go Deep | Wireshark • wnpa-sec-2026-17 RDP dissector crash

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

RDP ZGFX Heap Buffer Overflow (#21105) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/issues/21105

Vendor Advisories for CVE-2026-5405(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatwireshark-1:4.4.2-3.el10_0.42026-06-16redhat
redhatwireshark-1:4.4.2-10.el10_22026-05-26redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wireshark3.4.10-0+deb11u1 ... 4.6.6-2 (69 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wireshark4.0.10-1 ... 4.0.8-1 (12 versions)4.0.17-0+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wireshark4.4.13-0+deb13u1, 4.4.14-0+deb13u1, 4.4.7-1, 4.4.8-0exp1, 4.4.9-14.4.15-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wireshark4.4.7-1 ... 4.6.4-1 (13 versions)4.6.5-1—

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 244 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-5405?
CVE-2026-5405 is a high vulnerability published on May 1, 2026. RDP protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service and possible code execution
When was CVE-2026-5405 disclosed?
CVE-2026-5405 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5405 actively exploited?
CVE-2026-5405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-5405?
CVE-2026-5405 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-5405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5405, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-5405?

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

Start Free Scan →Browse All CVEs