CVE-2026-50527

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:microsoft, epss
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Stack-based buffer overflow in .NET Framework allows an unauthorized attacker to deny service over a network.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 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-50527

Vendor Advisories for CVE-2026-50527(19)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.110-10.0.10-0ubuntu1~26.04.1) @ resolute2026-08-30ubuntu
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8-0-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el9_82026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el10_22026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el10_22026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el8_102026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet9-0-main-9.0.118-1.hum12026-06-19redhat
redhatdotnet10-0-main-10.0.109-1.hum12026-06-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
System.Security.Cryptography.Xml8.0.0, 8.0.1, 8.0.2, 8.0.38.0.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 24× in last 7d / 123× 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 175 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50527?
CVE-2026-50527 is a high vulnerability published on July 14, 2026. Stack-based buffer overflow in .NET Framework allows an unauthorized attacker to deny service over a network.
When was CVE-2026-50527 disclosed?
CVE-2026-50527 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-50527 actively exploited?
CVE-2026-50527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.1% of all scored CVEs.
What is the CVSS score of CVE-2026-50527?
CVE-2026-50527 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50527?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50527, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50527

Explore →

Is Your Infrastructure Affected by CVE-2026-50527?

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

Start Free Scan →Browse All CVEs