Cyber Resilience

CVE-2026-0960

DoS in Wireshark 4.4.0 – 4.4.13

Public PoCDoS
Published
14 January 2026
Modified
21 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0012 2th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-0960 is a medium-severity Infinite Loop (CWE-835) vulnerability in Wireshark Wireshark. Its CVSS base score is 4.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and CM-7 (Least Functionality) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

HTTP3 protocol dissector infinite loop in Wireshark 4.6.0 to 4.6.2 allows denial of service

CWE(s)
CWE-835

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
Why these techniques?

Infinite loop in Wireshark HTTP/3 dissector directly enables crafted traffic to crash/hang the application, matching Application or System Exploitation for endpoint DoS.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-6521Same product: Wireshark Wireshark
CVE-2026-6531Same product: Wireshark Wireshark
CVE-2026-15163Same product: Wireshark Wireshark
CVE-2026-6528Same product: Wireshark Wireshark
CVE-2026-6534Same product: Wireshark Wireshark
CVE-2026-6522Same product: Wireshark Wireshark
CVE-2026-6536Same product: Wireshark Wireshark
CVE-2026-6523Same product: Wireshark Wireshark
CVE-2026-6519Same product: Wireshark Wireshark
CVE-2026-7375Same product: Wireshark Wireshark

Affected Assets

wireshark
wireshark
4.4.0 — 4.4.13 · 4.6.0 — 4.6.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • CM-7 Least Functionality
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires timely application of vendor patches that fix the HTTP/3 infinite-loop flaw in Wireshark.

CM-7 Least Functionality partial match
prevent

Enforces least functionality by restricting or sandboxing use of Wireshark against untrusted captures that trigger the loop.

SI-4 System Monitoring partial match
detect

Enables monitoring for anomalous CPU or resource exhaustion caused by the Wireshark dissector hang.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can uncover infinite-loop conditions before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address loop termination and prevent infinite loops.

A.8.27 Secure system architecture and engineering principles none match
none

Secure architecture principles encourage designs that avoid unreachable exit conditions.

A.8.32 Change management none match
none

Change management can require review of loop logic when code is modified.

References