CVE-2026-49172

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. The CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
9.8EG
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: 1.0%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Heap-based buffer overflow in Windows FTP Service allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.0% × 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 total (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
1.0%
EPSS %ILE
61st
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 total (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)3 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 total (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 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-49172

Vendor Advisories for CVE-2026-49172(2)

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 21× in last 7d / 64× 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 649 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 549 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49172?
CVE-2026-49172 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Heap-based buffer overflow in Windows FTP Service allows an unauthorized attacker to execute code over a network.
When was CVE-2026-49172 made public?
CVE-2026-49172 was made public on July 14, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-49172 actively exploited?
CVE-2026-49172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49172?
CVE-2026-49172 has a CVSS base score of 9.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-49172?
A fix for CVE-2026-49172 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49172 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49172?

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

Book a Demo →Browse All CVEs