CVE-2026-15168: Use of Uninitialized Variable in Wireshark
Published Jul 8, 2026
·Updated
BLF file parser in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows possible information disclosure
Affected Software
3 affected components
Wireshark Wireshark>=4.6.0<=4.6.6, >=4.4.0<=4.4.16
Wireshark Wireshark>=4.4.0<4.4.17
Wireshark Wireshark>=4.6.0<4.6.7
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wiresharkto a version that resolves this vulnerability.Fixed in 4.6.7
Event History
Jul 8, 2026
CVE Published
via MITRE·09:47 PM
Data Sourced
via MITRE·09:47 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-15168?
CVE-2026-15168 is classified as low severity with a score of 2.5.
2
How does CVE-2026-15168 affect Wireshark?
CVE-2026-15168 allows possible information disclosure due to the use of uninitialized variables in the BLF file parser.
3
Which versions of Wireshark are affected by CVE-2026-15168?
CVE-2026-15168 affects Wireshark versions 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16.
4
How do I fix CVE-2026-15168?
To resolve CVE-2026-15168, update to the latest version of Wireshark that is not affected by this vulnerability.
5
Is there a workaround for CVE-2026-15168?
Currently, there is no official workaround for CVE-2026-15168 besides updating Wireshark to a secure version.