CVE-2026-5405
Wireshark buffer overflow
- Published30 Apr 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:20600
- https://access.redhat.com/errata/RHSA-2026:26182
- https://access.redhat.com/security/cve/CVE-2026-5405
- https://bugzilla.redhat.com/show_bug.cgi?id=2464273
- https://gitlab.com/wireshark/wireshark/-/issues/21105
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5405.json
- https://www.wireshark.org/security/wnpa-sec-2026-17.html
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-5405 being actively exploited?
CVE-2026-5405 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.19%.
How severe is CVE-2026-5405?
CVE-2026-5405 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.19% probability of exploitation.
Which products are affected by CVE-2026-5405?
Affected products include Wireshark.
How do I fix CVE-2026-5405?
Upgrade affected software to a fixed version, for example Wireshark 4.4.15 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-5405 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.