CVE-2026-50416

LOWNVD 3.33.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated
3.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 3.3Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Exposure of sensitive information to an unauthorized actor in Windows Win32K allows an authorized attacker to disclose information locally.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
31
EG Risk 31/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)
Severity33% × 45%
The EG Score, 3.3 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 every mission impact level.
Exploitation none (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (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 14, 2026

Last Modified

October 8, 2026

References (1)

Vendor Advisories for CVE-2026-50416(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 14× in last 7d / 42× 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 199 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 99 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.5% · 37th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  10. 2026-10-08 19:28 UTCEG score recompute
  11. 2026-10-08 19:28 UTCVendor advisory
  12. 2026-10-08 19:28 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-10-01 13:05 UTCEG score recompute
  22. 2026-10-01 13:05 UTCVendor advisory
  23. 2026-10-01 13:05 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 75 more
  1. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  2. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  4. 2026-09-25 19:02 UTCEG score recompute
  5. 2026-09-25 19:02 UTCVendor advisory
  6. 2026-09-25 19:02 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  7. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-09-23 03:45 UTCEG score recompute
  9. 2026-09-23 03:45 UTCVendor advisory
  10. 2026-09-23 03:45 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  12. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-09-17 23:16 UTCEG score recompute
  14. 2026-09-17 23:16 UTCVendor advisory
  15. 2026-09-17 23:16 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-09-13 07:48 UTCEG score recompute
  20. 2026-09-13 07:48 UTCVendor advisory
  21. 2026-09-13 07:48 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  22. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-09-09 22:49 UTCEG score recompute
  25. 2026-09-09 22:49 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  26. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  27. 2026-09-08 21:58 UTCVendor advisory
  28. 2026-09-08 21:57 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  29. 2026-09-08 01:32 UTCEG score recompute
  30. 2026-09-08 01:32 UTCVendor advisory
  31. 2026-09-08 01:32 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  34. 2026-09-04 23:06 UTCEG score recompute
  35. 2026-09-04 23:06 UTCVendor advisory
  36. 2026-09-04 23:05 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  38. 2026-09-02 19:50 UTCEG score recompute
  39. 2026-09-02 19:50 UTCVendor advisory
  40. 2026-09-02 19:50 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  41. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  43. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  44. 2026-08-31 16:05 UTCEG score recompute
  45. 2026-08-31 16:05 UTCVendor advisory
  46. 2026-08-31 16:05 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  47. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  49. 2026-08-28 23:11 UTCEG score recompute
  50. 2026-08-28 23:11 UTCVendor advisory
  51. 2026-08-28 23:11 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  53. 2026-08-27 21:32 UTCEG score recompute
  54. 2026-08-27 21:32 UTCVendor advisory
  55. 2026-08-27 21:32 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  56. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  57. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  59. 2026-08-24 21:13 UTCEG score recompute
  60. 2026-08-24 21:13 UTCVendor advisory
  61. 2026-08-24 21:13 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  62. 2026-08-23 14:25 UTCEG score recompute
  63. 2026-08-23 14:25 UTCVendor advisory
  64. 2026-08-23 14:25 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  66. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-08-20 17:08 UTCVendor advisory
  69. 2026-08-20 17:08 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  70. 2026-08-19 17:06 UTCEG score recompute
  71. 2026-08-19 17:06 UTCVendor advisory
  72. 2026-08-19 17:06 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3
  73. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  74. 2026-08-19 15:52 UTCVendor advisory
  75. 2026-08-19 15:52 UTCGHSA enrichmentGHSA-x47j-8c8r-mqm2 · GitHub severity LOW · GitHub CVSS 3.3

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCkarollooool/CVE-2026-50416-writeup-and-poc
    Published Jul 17, 2026

    CVE-2026-50416: Windows 11 KASLR bypass

    Open source ↗
  • GitHub PoCZeroDayEvil/CVE-2026-50416-writeup-and-PoC
    Published Feb 5, 2026
    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50416?
CVE-2026-50416 is a low-severity vulnerability; its CVE record was published on July 14, 2026. Exposure of sensitive information to an unauthorized actor in Windows Win32K allows an authorized attacker to disclose information locally.
When was CVE-2026-50416 made public?
CVE-2026-50416 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-50416 actively exploited?
CVE-2026-50416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50416?
CVE-2026-50416 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-50416?
A fix for CVE-2026-50416 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50416 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50416?

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

Book a Demo →Browse All CVEs