CVE-2026-50526

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 86% 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: epss, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

Improper link resolution before file access ('link following') in .NET allows an authorized attacker to perform tampering locally.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
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-50526

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.110-10.0.10-0ubuntu1~26.04.1) @ resolute2026-09-17ubuntu
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-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-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet8.0-0:8.0.129-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
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
Microsoft.NET.Build.Containers8.0.29

Weakness Classification(2)

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 10× in last 7d / 65× 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 162 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50526?
CVE-2026-50526 is a medium vulnerability published on July 14, 2026. Improper link resolution before file access ('link following') in .NET allows an authorized attacker to perform tampering locally.
When was CVE-2026-50526 disclosed?
CVE-2026-50526 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-50526 actively exploited?
CVE-2026-50526 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 86.2% of all scored CVEs.
What is the CVSS score of CVE-2026-50526?
CVE-2026-50526 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-50526?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50526, 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-50526

Explore →

Is Your Infrastructure Affected by CVE-2026-50526?

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