CVE-2026-60108

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-09. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Zeek before 8.0.9 contains an uncontrolled memory consumption vulnerability in the FTP analyzer that allows unauthenticated remote attackers to cause process termination by sending a crafted FTP control session negotiating AUTH GSSAPI followed by a large ADAT control line. Attackers can exploit the NVT_Analyzer component's lack of a maximum line length check, causing it to continuously double its internal buffer without bounds during base64 decoding of an attacker-controlled ADAT token, resulting in denial of service of the Zeek sensor.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 9, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
Patch available. Sources: github_release, github_commit.
Web page

Zeek < 8.0.9 Uncontrolled Memory Consumption DoS via FTP Analyzer | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zeek-uncontrolled-memory-consumption-dos-via-ftp-analyzer
GitHub commit Patch Available

commit 93ff6950a90c (zeek/zeek)

Patch available: zeek/zeek v8.0.9 (contains commit 93ff6950a90c)

https://github.com/zeek/zeek/commit/93ff6950a90cfa9d00c1062cde429313a0402a01
GitHub release Patch Available

v8.0.9

Patch available: zeek/zeek v8.0.9

https://github.com/zeek/zeek/releases/tag/v8.0.9

Vendor Advisories for CVE-2026-60108(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 13× in last 7d / 39× 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 232 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 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-60108?
CVE-2026-60108 is a high-severity vulnerability; its CVE record was published on July 9, 2026. Zeek before 8.0.9 contains an uncontrolled memory consumption vulnerability in the FTP analyzer that allows unauthenticated remote attackers to cause process termination by sending a crafted FTP control session negotiating AUTH GSSAPI followed by a large ADAT control line. Attackers can exploit the…
When was CVE-2026-60108 made public?
CVE-2026-60108 was made public on July 6, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 9, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-60108 actively exploited?
CVE-2026-60108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60108?
CVE-2026-60108 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-60108?
A fix for CVE-2026-60108 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60108 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-60108?

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

Book a Demo →Browse All CVEs