CVE-2026-15168

LOWNVD 3.32.5▼
EchelonGraph scoreHIGH confidence

Score 2.5 from GitHub Security Advisory (severity: LOW) published 2026-07-09. NVD baseline CVSS 3.3; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
3.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
3.3
EG Score
2.5(high)
EPSS
1.2%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

References (3)

Vendor Advisories for CVE-2026-15168(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 13:34 UTCEG score recompute
  4. 2026-07-14 13:34 UTCGHSA enrichment
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:12 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 17:49 UTCEG score recompute
  9. 2026-07-11 17:49 UTCGHSA enrichment
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:36 UTCNVD updateCVSS v3 → 3.3
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 22:04 UTCEG score recompute
  14. 2026-07-08 22:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15168?
CVE-2026-15168 is a low vulnerability published on July 8, 2026. BLF file parser in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows possible information disclosure
When was CVE-2026-15168 disclosed?
CVE-2026-15168 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15168 actively exploited?
CVE-2026-15168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15168?
CVE-2026-15168 has a CVSS v3 base score of 3.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 2.5.
How do I remediate CVE-2026-15168?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15168, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15168

Explore →

Is Your Infrastructure Affected by CVE-2026-15168?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs