CVE-2026-15173

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-08) is not newer than that change (2026-07-09), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

Upgrade to version 4.6.7 or above (from the CVE record's solution, GitLab Inc.) — apply it.

pcapng file parser crash in Wireshark 4.6.0 to 4.6.6 allows denial of service

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade to version 4.6.7 or above (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

Upgrade to version 4.6.7 or above (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 8, 2026
Fix named in the CVE record's solution (GitLab Inc.).
Web page

Darwin DPIB UUID option rewrite heap overflow (#21285) · Issues · Wireshark Foundation / Wireshark · GitLab

https://gitlab.com/wireshark/wireshark/-/work_items/21285

Vendor Advisories for CVE-2026-15173(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark3.4.10-0+deb11u1 ... 4.6.6-2 (69 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.0.10-1 ... 4.6.6-2 (50 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.4.13-0+deb13u1 ... 4.6.6-2 (20 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wireshark4.4.7-1 ... 4.6.6-2 (16 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 149 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-12 16:32 UTCEG score recompute
  4. 2026-10-11 20:10 UTCEG score recompute
  5. 2026-10-11 17:22 UTCEG score recompute
  6. 2026-10-11 14:55 UTCEG score recompute
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-01 16:09 UTCEG score recompute
  17. 2026-10-01 16:09 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-28 13:20 UTCEG score recompute
  22. 2026-09-28 13:20 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  23. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-24 11:44 UTCEG score recompute
Show 75 more
  1. 2026-09-24 11:44 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  2. 2026-09-23 06:04 UTCEG score recompute
  3. 2026-09-23 06:04 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  4. 2026-09-18 19:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-09-18 05:41 UTCEG score recompute
  6. 2026-09-18 05:41 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  7. 2026-09-16 14:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-16 05:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-09-14 11:14 UTCEG score recompute
  10. 2026-09-14 11:14 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  11. 2026-09-13 16:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-09-13 08:23 UTCEG score recompute
  13. 2026-09-13 08:23 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  14. 2026-09-12 15:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-09-12 03:30 UTCEG score recompute
  16. 2026-09-12 03:30 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  17. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-09-11 09:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-09-10 09:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-09-08 22:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-09-06 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-09-05 22:46 UTCEG score recompute
  23. 2026-09-05 22:46 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  24. 2026-09-04 05:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  25. 2026-09-01 13:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  26. 2026-08-30 07:28 UTCEG score recompute
  27. 2026-08-30 07:28 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  28. 2026-08-30 01:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-08-28 21:41 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  30. 2026-08-27 21:48 UTCEG score recompute
  31. 2026-08-27 21:48 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  32. 2026-08-27 14:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  33. 2026-08-26 14:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  34. 2026-08-26 04:45 UTCEG score recompute
  35. 2026-08-26 04:45 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  36. 2026-08-25 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  37. 2026-08-24 23:52 UTCEG score recompute
  38. 2026-08-24 23:52 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  39. 2026-08-23 21:49 UTCEG score recompute
  40. 2026-08-23 21:49 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  41. 2026-08-23 00:19 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  42. 2026-08-22 19:46 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  43. 2026-08-21 17:43 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  44. 2026-08-20 15:39 UTCEG score recompute
  45. 2026-08-20 15:39 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  47. 2026-08-19 13:36 UTCEG score recompute
  48. 2026-08-19 13:36 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  49. 2026-08-18 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  50. 2026-08-18 11:32 UTCEG score recompute
  51. 2026-08-18 11:32 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  52. 2026-08-17 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  53. 2026-08-17 09:22 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  54. 2026-08-16 07:20 UTCEG score recompute
  55. 2026-08-16 07:20 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  57. 2026-08-15 05:17 UTCEG score recompute
  58. 2026-08-15 05:17 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  60. 2026-08-14 03:13 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  61. 2026-08-13 01:11 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  62. 2026-08-11 23:08 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  63. 2026-08-10 21:05 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  64. 2026-08-09 19:02 UTCEG score recompute
  65. 2026-08-09 19:02 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  67. 2026-08-08 16:59 UTCEG score recompute
  68. 2026-08-08 16:59 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  69. 2026-08-08 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  70. 2026-08-07 14:55 UTCEG score recompute
  71. 2026-08-07 14:55 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  72. 2026-08-06 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  73. 2026-08-06 12:52 UTCEG score recompute
  74. 2026-08-06 12:52 UTCGHSA enrichmentGHSA-qq69-vqh3-gr8r · GitHub CVSS 4.7
  75. 2026-08-05 19:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2026-15173?
CVE-2026-15173 is a medium-severity vulnerability; its CVE record was published on July 8, 2026. pcapng file parser crash in Wireshark 4.6.0 to 4.6.6 allows denial of service
When was the CVE record for CVE-2026-15173 published?
The CVE record for CVE-2026-15173 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 9, 2026; the record at its source may have been updated since.
Is CVE-2026-15173 actively exploited?
CVE-2026-15173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15173?
CVE-2026-15173 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-15173?
The CVE record's solution for CVE-2026-15173, written by its CNA GitLab Inc., names the fix: "Upgrade to version 4.6.7 or above". The vendor advisories EchelonGraph has for CVE-2026-15173 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15173

Explore →

Is Your Infrastructure Affected by CVE-2026-15173?

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