CVE-2026-3203 | Buffer Over-read in Wireshark

RF4CE Profile protocol dissector crash in Wireshark 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13 allows denial of service

Published: 2026-02-25 Last update: 2026-02-26 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-3203 is rated Low Risk (22.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-3203

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-26 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-3203

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-3203

OS Trackers for CVE-2026-3203

vendor priority summary link
alpine — CVE-2026-3203: 1 source package rows (wireshark); 14 state rows across 2 repos (3.23-community, edge-community); fixed 1, open 13. https://security.alpinelinux.org/vuln/CVE-2026-3203
debian not yet assigned CVE-2026-3203 not yet assigned priority: Debian including 1 source packages (wireshark), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2026-3203
redhat medium — https://access.redhat.com/security/cve/CVE-2026-3203
suse low CVE-2026-3203 severity low: SUSE including 61 source package names (libvirt-11.0.0-150700.4.19.1, libvirt-client-11.0.0-150700.4.19.1, …), 155 product×package rows across 23 product lines (Image SLES15-SP7-SAP-EC2, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (23 product lines)): Known Not Affected 106, Fixed 49. https://www.suse.com/security/cve/CVE-2026-3203/
ubuntu medium CVE-2026-3203 medium priority: Ubuntu including 1 source packages (wireshark), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 8. https://ubuntu.com/security/CVE-2026-3203

Affected software / configurations for CVE-2026-3203

Vendor Product Version Raw CPE
wireshark wireshark >= 4.4.0, < 4.4.14 cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*
wireshark wireshark >= 4.6.0, < 4.6.4 cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*

References for CVE-2026-3203

cvelogic Threat Intelligence