CVE-2026-49791

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

Improper link resolution before file access ('link following') in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 14, 2026

Last Modified

September 17, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-49791(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 11× in last 7d / 99× 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.

Showing the most recent 100 of 291 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-49791?
CVE-2026-49791 is a high vulnerability published on July 14, 2026. Improper link resolution before file access ('link following') in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to elevate privileges locally.
When was CVE-2026-49791 disclosed?
CVE-2026-49791 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49791 actively exploited?
CVE-2026-49791 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.1% of all scored CVEs.
What is the CVSS score of CVE-2026-49791?
CVE-2026-49791 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-49791?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49791, 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-49791

Explore →

Is Your Infrastructure Affected by CVE-2026-49791?

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