CVE-2026-3201

MEDIUMNVD 7.54.7▼
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-02-25. the CNA's CVSS baseline 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:gitlab, ghsa
Trending — 5 sources updated this week
4.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

USB HID protocol dissector memory exhaustion in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service

CVSS v3
7.5
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 17, 2026

References (2)

Vendor Advisories for CVE-2026-3201(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatwireshark-1:4.4.2-3.el10_0.42026-06-16redhat
redhatwireshark-1:4.4.2-4.el10_1.42026-04-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 12:55 UTCEG score recompute
  3. 2026-07-27 12:55 UTCVendor advisory
  4. 2026-07-27 12:55 UTCGHSA enrichment
  5. 2026-07-27 12:50 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-3201?
CVE-2026-3201 is a medium vulnerability published on February 25, 2026. USB HID protocol dissector memory exhaustion in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service
When was CVE-2026-3201 disclosed?
CVE-2026-3201 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3201 actively exploited?
CVE-2026-3201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.7% of all scored CVEs.
What is the CVSS score of CVE-2026-3201?
CVE-2026-3201 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.7.
How do I remediate CVE-2026-3201?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3201, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3201

Explore →

Is Your Infrastructure Affected by CVE-2026-3201?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs