CVE-2026-15168: Wireshark BLF Parser Information Disclosure (CVSS 2.5)
Wireshark's BLF (Binary Logging Format) file parser in recent versions contains a flaw that could leak sensitive information when a user opens a specially crafted BLF file. An attacker would need to trick a user into opening a malicious file locally—this is not a remote attack and requires user interaction. The risk is limited to potential disclosure of small amounts of data; the vulnerability does not enable system compromise, privilege escalation, or denial of service.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 2.5 LOW · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
- Weaknesses (CWE)
- CWE-457
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-07-08 / 2026-07-09
NVD description (verbatim)
BLF file parser in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows possible information disclosure
3 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-15168 is a CWE-457 (Use of Uninitialized Variable) flaw in Wireshark's BLF file parser. The vulnerability exists in versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16. A crafted BLF file can trigger uninitialized variable access during parsing, potentially exposing small amounts of memory contents. The attack surface is local only; exploitation requires a user with Wireshark installed to manually open a malicious file. The vulnerability does not affect the integrity or availability of the system.
Business impact
This vulnerability poses minimal business risk for most organizations. Wireshark is primarily a traffic analysis and troubleshooting tool used by network engineers and security analysts. A real-world attack would require social engineering (convincing a user to open a suspicious BLF file), and the information disclosure is limited in scope. Organizations where Wireshark is used in security operations centers or for incident response should patch to reduce the attack surface, but this is not a critical or urgent business risk.
Affected systems
Wireshark versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16 are affected. Consult the official Wireshark security advisory and download page to confirm patched versions available for your deployment. Organizations running Wireshark on Windows, Linux, or macOS systems should inventory instances and prioritize updates for systems handling untrusted network capture files.
Exploitability
Exploitability is low. The attack requires local file access and user interaction; an attacker must convince a Wireshark user to open a crafted BLF file. There is no remote exploitation path, no network trigger, and no privilege requirement. The CVSS vector (AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N) reflects this: attack vector is local, attack complexity is high, user interaction is required, and impact is limited to confidentiality. No public exploit code has been referenced, and this vulnerability has not been added to the CISA KEV (Known Exploited Vulnerabilities) catalog.
Remediation
Update Wireshark to a patched version released after July 8, 2026. For the 4.6 branch, upgrade to 4.6.7 or later; for the 4.4 branch, upgrade to 4.4.17 or later. Verify exact patched versions in the official Wireshark security advisory. Until patching is complete, limit user access to Wireshark on systems handling untrusted BLF files and educate users not to open BLF files from unknown sources.
Patch guidance
Check the Wireshark website and security advisories for patched releases addressing CVE-2026-15168. Wireshark provides binary packages for Windows, macOS, and Linux distributions. For enterprise deployments, coordinate updates through your standard change management process. Given the low CVSS score and local-only attack surface, this update can be prioritized after critical and high-severity patches but should be scheduled within 30–60 days.
Detection guidance
Monitor for suspicious BLF files being opened by Wireshark processes, particularly from email attachments, downloads, or external file shares. Endpoint detection and response (EDR) tools can flag unusual file access patterns following BLF parsing. Log Wireshark process execution with file arguments to detect user opening of unexpected BLF sources. Application whitelisting or sandboxing can restrict Wireshark to only trusted file locations.
Why prioritize this
This vulnerability ranks as low priority due to its narrow attack surface (local, user-interactive), limited impact (information disclosure only), and low CVSS score of 2.5. It does not affect system availability or enable code execution. Patching should be scheduled as part of routine maintenance, not as an emergency response. However, organizations where Wireshark handles sensitive network captures or is exposed to untrusted file sources should prioritize this update slightly higher.
Risk score, explained
The CVSS v3.1 score of 2.5 (LOW) accurately reflects the vulnerability's limited threat. The local attack vector (AV:L), high attack complexity (AC:H), and required user interaction (UI:R) significantly constrain exploitation. Confidentiality impact (C:L) is the only harm dimension affected, and only to a low degree. The unchanged integrity (I:N) and availability (A:N) ratings confirm no system compromise or outage risk.
Frequently asked questions
Can this vulnerability be exploited remotely?
No. CVE-2026-15168 requires local file access and manual user action. An attacker must trick a Wireshark user into opening a malicious BLF file; it cannot be triggered over the network.
What types of information could be disclosed?
The uninitialized variable flaw may expose small amounts of memory contents that Wireshark allocates during parsing. The scope is limited; this is not a wholesale data dump vulnerability. The actual leaked data depends on memory state at parse time.
Is patching urgent for my organization?
Not critical. Given the low CVSS score and user-interaction requirement, patching is important but can be scheduled as part of regular maintenance cycles. Organizations handling many untrusted BLF files or with high-security requirements should accelerate their patch timeline to 30 days.
Does this vulnerability appear on the CISA KEV list?
No. As of the publication date, CVE-2026-15168 has not been added to the CISA Known Exploited Vulnerabilities catalog, indicating no observed active exploitation in the wild.
This analysis is based on data available as of July 9, 2026. Patch version numbers and availability should be verified against official Wireshark security advisories and release notes before deployment. SEC.co does not distribute exploit code or weaponized proof-of-concept materials. Organizations should conduct internal risk assessments based on their specific Wireshark deployment, threat model, and file-handling practices. This summary is for informational purposes and does not constitute professional security advice for your environment. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-47330LOWAppArmor Cache Poisoning in Ubuntu Linux 6.8, 7.0, 7.17
- CVE-2026-47336LOWAppArmor Socket Mediation Bypass in Ubuntu Linux 6.8
- CVE-2026-9920LOWChrome Android GPU Memory Leak Vulnerability
- CVE-2026-9944LOWChrome ANGLE Memory Leak Cross-Origin Data Disclosure
- CVE-2026-10008MEDIUMChrome Android GPU Memory Disclosure Vulnerability
- CVE-2026-10960HIGHChrome Sandbox Escape via Uninitialized Codec Variable
- CVE-2026-10973HIGHChrome Cross-Origin Data Leak via Uninitialized Memory
- CVE-2026-10976HIGHChrome Uninitialized Use Memory Disclosure Vulnerability (CVSS 7.4)