CVE-2026-5407Public exploit

Service hang via cyclic SMB2 record offsets

Published Apr 30, 2026 · Updated Apr 30, 2026

Infinite looping in the SMB2 dissector in Wireshark 4.4.0 through 4.4.14 and 4.6.0 through 4.6.4 allows attackers to hang analysis. The dissect_smb2_notify_data_out and dissect_smb2_file_full_ea_info functions add packet-supplied next_offset values without rejecting backward movement, allowing 32-bit wraparound to cycle between records indefinitely. A malformed packet injected onto a captured network or opened from a trace file keeps Wireshark or TShark at full CPU until the process is forcibly terminated; live exploitation requires the target to capture the traffic, while file exploitation requires user interaction.

CVSS severity5.5
Medium
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Infinite looping in the SMB2 dissector in Wireshark 4.4.0 through 4.4.14 and 4.6.0 through 4.6.4 allows attackers to hang analysis. The dissect_smb2_notify_data_out and dissect_smb2_file_full_ea_info functions add packet-supplied next_offset values without rejecting backward movement, allowing 32-bit wraparound to cycle between records indefinitely. A malformed packet injected onto a captured network or opened from a trace file keeps Wireshark or TShark at full CPU until the process is forcibly terminated; live exploitation requires the target to capture the traffic, while file exploitation requires user interaction.

The record

CVE
CVE-2026-5407
Published
Apr 30, 2026
Updated
Apr 30, 2026
Vendor
Wireshark Foundation
Product
Wireshark
Classifications
CWE-835, T1499
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 30, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 30, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.4.0 <4.4.15
  2. Affected versionversion=4.6.0 <4.6.5

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Wireshark Foundation · Wiresharkversion=4.4.0 <4.4.15; version=4.6.0 <4.6.5

Published CVSS scores

5.5GitLab Inc.CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-835Loop with Unreachable Exit Condition ('Infinite Loop')
T1499Endpoint Denial of Service

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo