CVE-2026-50416

LOWNVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
Trending — 4 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

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

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.3(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 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 17× in last 7d / 77× 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 127 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

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

    CVE-2026-50416: Windows 11 KASLR bypass

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50416?
CVE-2026-50416 is a low vulnerability 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 disclosed?
CVE-2026-50416 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50416 actively exploited?
CVE-2026-50416 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 62.1% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50416, 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-50416

Explore →

Is Your Infrastructure Affected by CVE-2026-50416?

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

Start Free Scan →Browse All CVEs