Security readout for executives and security teams
Plain-English summary
CVE-2026-0960 is a Wireshark denial-of-service issue in the HTTP/3 dissector. A malicious or malformed HTTP/3 capture could cause Wireshark to enter an infinite loop, making the application unavailable. Business impact is mainly analyst workstation disruption, not data theft or system takeover based on the provided sources.
Executive priority
Treat as a targeted operational reliability issue for security, network, and engineering teams using Wireshark. It does not currently justify emergency enterprise-wide response, but affected analyst workstations should be identified and remediated through normal vulnerability management priority.
Technical view
The vulnerability is CWE-835, an infinite loop in Wireshark’s HTTP/3 protocol dissector. Reported affected versions are Wireshark 4.6.0 through 4.6.2. CVSS 3.1 is 4.7: local attack vector, high complexity, no privileges, user interaction required, and high availability impact only.
Likely exposure
Exposure is most relevant where analysts open packet captures or inspect traffic containing HTTP/3 data in affected Wireshark versions. Servers are not directly exposed simply by running HTTP/3; the risk centers on Wireshark users processing crafted input.
Exploitation context
The provided sources do not indicate active exploitation, and the CVE is not listed as CISA KEV. Exploitation requires a user to process relevant crafted data in Wireshark, so phishing, shared captures, or untrusted troubleshooting files are plausible delivery paths.
Researcher notes
The GitLab issue is marked permissions-required in the provided bundle, limiting independent technical detail. Do not assume exploit availability or specific fixed versions from the bundle alone. The strongest facts are the CVE description, CVSS vector, CWE, affected range, and Wireshark advisory reference.
Mitigation direction
- Identify Wireshark installations running 4.6.0 through 4.6.2.
- Check the Wireshark advisory for vendor-confirmed fixed versions or workarounds.
- Prioritize updating analyst systems that process untrusted packet captures.
- Avoid opening untrusted HTTP/3 captures until vendor guidance is applied.
- Restrict capture-sharing workflows to trusted sources where practical.
Validation and detection
- Inventory installed Wireshark versions across analyst and engineering workstations.
- Confirm whether teams process HTTP/3 packet captures or live traffic.
- Review Wireshark advisory WNPA-SEC-2026-04 for official remediation status.
- Verify affected versions are upgraded or otherwise covered by vendor guidance.
- Monitor CVE and vendor pages for updates or exploitation reports.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-835: 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 lookupCVE-2026-0960 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H13.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.7MediumVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wireshark.org/security/wnpa-sec-2026-04.htmlCVE reference
- GitLab Issue #20944CVE reference · issue-tracking, permissions-required
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Loop with Unreachable Exit Condition ('Infinite Loop')
Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.