CVE-2026-3203: Buffer Over-read in Wireshark
Published Feb 25, 2026
·Updated
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
Affected Software
3 affected components
Wireshark Wireshark>=4.6.0<=4.6.3, >=4.4.0<=4.4.13
Wireshark Wireshark>=4.4.0<4.4.14
Wireshark Wireshark>=4.6.0<4.6.4
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wiresharkto a version that resolves this vulnerability.Fixed in 4.6.4
Event History
Feb 25, 2026
CVE Published
via MITRE·02:36 PM
Data Sourced
via MITRE·02:36 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via Red Hat·03:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:20 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-3203?
CVE-2026-3203 is classified as a denial of service vulnerability with a medium level of severity.
2
How do I fix CVE-2026-3203?
To fix CVE-2026-3203, upgrade your Wireshark installation to version 4.6.4 or later.
3
What versions of Wireshark are affected by CVE-2026-3203?
CVE-2026-3203 affects Wireshark versions 4.6.0 to 4.6.3 and 4.4.0 to 4.4.13.
4
What is the impact of CVE-2026-3203?
The impact of CVE-2026-3203 is that it may cause Wireshark to crash during parsing of certain RF4CE Profile protocol data.
5
Is CVE-2026-3203 a remote exploit?
CVE-2026-3203 is not classified as a remote exploit; it requires interaction with the vulnerable Wireshark application.