CVE-2026-5402

Heap-based Buffer Overflow in Wireshark

HIGH
8.8
CVSS Score
Published: April 30, 2026 at 05:39 AM UTC
Updated: October 26, 2026 at 12:10 AM UTC
1 product affected across 1 vendorWireshark

Using Wireshark by Wireshark Foundation?

Get instant alerts when new vulnerabilities affect Wireshark - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

TLS protocol dissector heap overflow in Wireshark 4.6.0 to 4.6.4 allows denial of service and possible code execution

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.6.0 ≤ v ≤ 4.6.44.6.0
Affected range stops below 4.6.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (5)

Issue TrackingPermissions RequiredExploit
Source: cverecord
https://gitlab.com/wireshark/wireshark/-/issues/21090
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-5402
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2464038

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHGitLab
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-122

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card