LiveActive security incident?Get immediate response
CVE Record

CVE-2026-5403: Heap-based Buffer Overflow in Wireshark

SBC codec 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

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Wireshark flaw where a crafted item processed by the SBC codec path can crash Wireshark and may allow code execution. The main business risk is to analyst workstations that open untrusted packet captures or traffic. There is no source evidence here of active exploitation.

Executive priority

Prioritize remediation for SOC, incident response, and engineering systems that process external captures. The issue is high severity because user interaction can still lead to crash or possible code execution on sensitive workstations.

Technical view

CVE-2026-5403 is a heap-based buffer overflow (CWE-122) in Wireshark 4.6.0-4.6.4 and 4.4.0-4.4.14. CVSS 3.1 is 7.8 with local attack vector, no privileges, and required user interaction. Reported impact is denial of service and possible code execution.

Likely exposure

Exposure is most likely on desktops, investigation VMs, SOC workstations, and lab systems running the affected Wireshark branches, especially where users open packet captures or data from untrusted sources.

Exploitation context

The CVSS vector requires local interaction by a user. The provided data says KEV is false and gives no cited evidence of exploitation in the wild. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

The source bundle identifies affected Wireshark ranges and CWE-122 but does not include detailed root cause, proof-of-concept status, or confirmed fixed release numbers. Avoid assuming exploitability beyond the stated denial of service and possible code execution.

Mitigation direction

  • Identify Wireshark 4.6.0-4.6.4 and 4.4.0-4.4.14 installations.
  • Apply Wireshark Foundation guidance for fixed versions or mitigations.
  • Avoid opening untrusted packet captures on vulnerable systems.
  • Use isolated analysis environments for suspicious captures until remediated.
  • Monitor vendor and OS distributor advisories for package status.

Validation and detection

  • Check installed Wireshark versions on analyst and engineering endpoints.
  • Confirm whether affected branches are present in software inventory.
  • Review package advisories from Wireshark and relevant distributors.
  • Verify updated systems no longer report affected versions.
  • Document any systems that must rely on temporary operational controls.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-5403 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9GitLab
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-5403Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPwireshark: Heap-based Buffer Overflow in Wireshark
other:Red Hat severity ratingcvssV3_1
  • 2026-05-01T00:00:55.928Z: Reported to Red Hat.
  • 2026-04-30T23:04:03.523Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Wireshark FoundationWireshark4.6.0, 4.4.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.