What is the CVSS score of CVE-2026-15168?

CVE-2026-15168 has a CVSS 3.1 base score of 3.3 (Low). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a patch available for CVE-2026-15168?

Yes, a patch is available for CVE-2026-15168. Update the affected software to the latest version immediately.

Wireshark CVE-2026-15168

EUVD-2026-42446 LOW

Use of Uninitialized Variable (CWE-457)

2026-07-08 cve@gitlab.com

GHSA-24h4-9r9x-fc93

Information Disclosure Wireshark

3.3

CVSS 3.1 · NVD

Severity by source

Vendor (gitlab) PRIMARY

LOW

qualitative

NVD

3.3 LOW

AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

vuln.today AI

2.5 LOW

File-open trigger requires local access and user action; high complexity for uninitialized-memory exploitation; no privileges needed on the system; confidentiality-only, limited-scope impact.

3.1 AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

4.0 AV:L/AC:H/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (gitlab).

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

CVSS changed

Jul 09, 2026 - 19:22 NVD

2.5 (LOW) 3.3 (LOW)

Patch available

Jul 08, 2026 - 23:04 EUVD

Analysis Generated

Jul 08, 2026 - 22:40 vuln.today

DescriptionNVD

BLF file parser in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows possible information disclosure

AnalysisAI

Information disclosure in Wireshark's BLF file parser affects versions 4.6.0-4.6.6 and 4.4.0-4.4.16, stemming from use of an uninitialized variable (CWE-457) that may expose portions of process memory when parsing a crafted BLF file. Exploitation is constrained by a local attack vector, high attack complexity, and mandatory user interaction - a victim must actively open a malicious file. With a CVSS score of 2.5, no CISA KEV listing, and no public exploit identified at time of analysis, this is a low-priority finding with a narrow, socially-engineered attack surface.

Technical ContextAI

BLF (Binary Logging Format) is a proprietary file format developed by Vector Informatik, widely used in automotive diagnostics for logging CAN bus and other vehicular network traffic. Wireshark supports offline parsing of BLF capture files, making it useful to automotive and embedded systems analysts. CWE-457 (Use of Uninitialized Variable) indicates the parser reads from a variable or buffer that has not been explicitly initialized before use, meaning its contents reflect residual heap or stack memory. When processing a specially crafted BLF file, an attacker can potentially shape those residual contents to leak sensitive in-process data - such as fragments of previously processed captures, keys, or other memory artifacts - into Wireshark's parsed output. The flaw spans both the 4.4.x long-term stable branch and the newer 4.6.x branch, confirmed by the Wireshark project's own security bulletin (wnpa-sec-2026-60.html) and associated GitLab work item.

RemediationAI

Users should upgrade to the next patched release beyond the affected ranges - consult the Wireshark security advisory at https://www.wireshark.org/security/wnpa-sec-2026-60.html for the exact fixed versions, as they were not explicitly stated in the provided references and cannot be independently confirmed from available data. As a fully effective workaround, avoid opening BLF files from untrusted sources in Wireshark; because exploitation requires user interaction to open the file, this eliminates the attack vector entirely with no operational side effects for analysts who do not routinely process externally-supplied BLF captures. Organizations that do process third-party BLF files should prioritize patching over relying on this behavioral control.