CVE-2026-50465

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

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

Improper access control in Microsoft Windows DNS allows an authorized attacker to perform tampering locally.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 30, 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-50465

Vendor Advisories for CVE-2026-50465(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 42× in last 7d / 71× 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.

  1. 2026-07-31 09:34 UTCVendor advisory
  2. 2026-07-31 09:34 UTCGHSA enrichment
  3. 2026-07-30 20:52 UTCGHSA enrichment
  4. 2026-07-30 19:58 UTCGHSA enrichment
  5. 2026-07-30 18:16 UTCEG score recompute
  6. 2026-07-30 18:16 UTCVendor advisory
  7. 2026-07-30 18:15 UTCGHSA enrichment
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 12:03 UTCEG score recompute
  10. 2026-07-30 12:03 UTCVendor advisory
  11. 2026-07-30 12:03 UTCGHSA enrichment
  12. 2026-07-30 01:30 UTCEPSS rescore
  13. 2026-07-29 23:13 UTCVendor advisory
  14. 2026-07-29 23:13 UTCGHSA enrichment
  15. 2026-07-29 10:31 UTCVendor advisory
  16. 2026-07-29 10:31 UTCGHSA enrichment
  17. 2026-07-28 21:47 UTCVendor advisory
  18. 2026-07-28 21:47 UTCGHSA enrichment
  19. 2026-07-28 16:02 UTCEG score recompute
  20. 2026-07-28 16:02 UTCVendor advisory
  21. 2026-07-28 16:02 UTCGHSA enrichment
  22. 2026-07-28 15:37 UTCEPSS rescore
  23. 2026-07-28 12:50 UTCVendor advisory
  24. 2026-07-28 12:50 UTCGHSA enrichment
  25. 2026-07-28 00:08 UTCVendor advisory
Show 46 more
  1. 2026-07-28 00:08 UTCGHSA enrichment
  2. 2026-07-27 22:30 UTCVendor advisory
  3. 2026-07-27 22:29 UTCGHSA enrichment
  4. 2026-07-27 16:29 UTCEG score recompute
  5. 2026-07-27 16:29 UTCVendor advisory
  6. 2026-07-27 16:29 UTCGHSA enrichment
  7. 2026-07-27 06:24 UTCVendor advisory
  8. 2026-07-27 06:24 UTCGHSA enrichment
  9. 2026-07-26 17:36 UTCEG score recompute
  10. 2026-07-26 17:36 UTCVendor advisory
  11. 2026-07-26 17:36 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 04:52 UTCEG score recompute
  14. 2026-07-26 04:52 UTCVendor advisory
  15. 2026-07-26 04:52 UTCGHSA enrichment
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 03:18 UTCEG score recompute
  20. 2026-07-22 14:08 UTCEPSS rescore
  21. 2026-07-21 15:25 UTCEPSS rescore
  22. 2026-07-20 17:08 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 03:08 UTCEG score recompute
  26. 2026-07-19 03:08 UTCVendor advisory
  27. 2026-07-19 03:08 UTCGHSA enrichment
  28. 2026-07-19 02:29 UTCEPSS rescore
  29. 2026-07-18 10:04 UTCEPSS rescore
  30. 2026-07-17 07:52 UTCEG score recompute
  31. 2026-07-17 07:52 UTCVendor advisory
  32. 2026-07-17 07:52 UTCGHSA enrichment
  33. 2026-07-16 20:37 UTCVendor advisory
  34. 2026-07-16 20:37 UTCGHSA enrichment
  35. 2026-07-16 17:03 UTCEPSS rescore
  36. 2026-07-16 07:55 UTCVendor advisory
  37. 2026-07-16 07:55 UTCGHSA enrichment
  38. 2026-07-15 19:12 UTCVendor advisory
  39. 2026-07-15 19:12 UTCGHSA enrichment
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-07-15 06:30 UTCVendor advisory
  43. 2026-07-15 06:30 UTCGHSA enrichment
  44. 2026-07-14 17:48 UTCEG score recompute
  45. 2026-07-14 17:48 UTCVendor advisory
  46. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50465?
CVE-2026-50465 is a high vulnerability published on July 14, 2026. Improper access control in Microsoft Windows DNS allows an authorized attacker to perform tampering locally.
When was CVE-2026-50465 disclosed?
CVE-2026-50465 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50465 actively exploited?
CVE-2026-50465 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 88.0% of all scored CVEs.
What is the CVSS score of CVE-2026-50465?
CVE-2026-50465 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50465?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50465, 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-50465

Explore →

Is Your Infrastructure Affected by CVE-2026-50465?

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

Start Free Scan →Browse All CVEs