Skip to content
Fencer Vulns
medium 4.7

CVE-2026-3201 json

Improperly Controlled Sequential Memory Allocation in Wireshark

published 2026-02-25 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8660

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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

Patch / fix

  • Wireshark Foundation Wireshark 4.4.14, 4.6.4
  • wireshark Debian 13 4.4.14-0+deb13u1
  • wireshark Debian 14 4.6.4-1

debian advisories DEBIAN-CVE-2026-3201

  • wireshark RHEL 10.1 1:4.4.2-4.el10_1.4
  • wireshark-cli RHEL 10.1 1:4.4.2-4.el10_1.4
  • wireshark enterprise linux eus 10.0 1:4.4.2-3.el10_0.4
  • wireshark-cli enterprise linux eus 10.0 1:4.4.2-3.el10_0.4

red hat advisories RHSA-2026:26182RHSA-2026:9666

  • wireshark SLE Module for Desktop Applications 15 SP7, SLE Module for Basesystem 15 SP7 4.6.4-150700.21.8.1
  • libvirt SLE Module for Server Applications 15 SP7, SLE Module for Basesystem 15 SP7 11.0.0-150700.4.19.1
  • wireshark openSUSE Leap 15.6 4.2.14-150600.18.38.1

suse advisories SUSE-SU-2026:1169-1SUSE-SU-2026:0810-1

  • wireshark openSUSE Tumbleweed 4.6.4-1.1

opensuse advisories openSUSE-SU-2026:10274-1

  • wireshark AlmaLinux 10 1:4.4.2-4.el10_1.4
  • wireshark-cli AlmaLinux 10 1:4.4.2-4.el10_1.4

almalinux advisories ALSA-2026:9666

  • wireshark Rocky Linux 10 1:4.4.2-4.el10_1.4

rocky linux advisories RLSA-2026:9666

  • wireshark Alpine 3.24, Alpine 3.23 4.6.4-r0

alpine advisories ALPINE-CVE-2026-3201

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-3201 updated cvss 5.5

wireshark: Improperly Controlled Sequential Memory Allocation in Wireshark

  • Red Hat Enterprise Linux AppStream (v. 10) wireshark 4.4.2-4.el10_1.4, wireshark-cli 4.4.2-4.el10_1.4
    fixed: vendor fix RHSA-2026:9666
  • Red Hat Enterprise Linux AppStream EUS (v. 10.0) wireshark 4.4.2-3.el10_0.4, wireshark-cli 4.4.2-3.el10_0.4
    fixed: vendor fix RHSA-2026:26182
  • Red Hat Enterprise Linux CodeReady Linux Builder (v. 10) wireshark-devel 4.4.2-4.el10_1.4, wireshark-debuginfo 4.4.2-4.el10_1.4, wireshark-debugsource 4.4.2-4.el10_1.4, wireshark-cli-debuginfo 4.4.2-4.el10_1.4
    fixed: vendor fix RHSA-2026:9666
  • Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0) wireshark-devel 4.4.2-3.el10_0.4, wireshark-debuginfo 4.4.2-3.el10_0.4, wireshark-debugsource 4.4.2-3.el10_0.4, wireshark-cli-debuginfo 4.4.2-3.el10_0.4
    fixed: vendor fix RHSA-2026:26182
  • Red Hat Enterprise Linux 6 wireshark, wireshark-gnome Red Hat Enterprise Linux 7 wireshark, wireshark-gnome Red Hat Enterprise Linux 8 wireshark, wireshark-cli Red Hat Enterprise Linux 9 wireshark, wireshark-cli
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • gitlab.com https://gitlab.com/wireshark/wireshark/-/issues/20972 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Wireshark Foundation Wireshark

Classification

Weakness
  • CWE-1325 Improperly Controlled Sequential Memory Allocation
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.