CVE-2026-62900

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). 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 — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

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
Severity59% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-62900

Vendor Advisories for CVE-2026-62900(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntudotnet10 (10.0.111-10.0.11-0ubuntu1~26.04.1) @ resolute2026-10-04ubuntu
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet10.0-0:10.0.111-1.el10_22026-08-17redhat
redhatdotnet10.0-0:10.0.111-1.el9_82026-08-17redhat
redhatdotnet9.0-0:9.0.120-1.el9_82026-08-17redhat
redhatdotnet8-0-main-8.0.130-0.1.hum12026-08-16redhat
redhatdotnet10-0-main-10.0.11-1.hum12026-08-15redhat
redhatdotnet8.0-0:8.0.130-1.el9_82026-08-13redhat
redhatdotnet10.0-0:10.0.111-1.el8_102026-08-13redhat
redhatdotnet9.0-0:9.0.120-1.el8_102026-08-13redhat
redhatdotnet8.0-0:8.0.130-1.el10_22026-08-13redhat
redhatdotnet9.0-0:9.0.120-1.el10_22026-08-13redhat
redhatdotnet8.0-0:8.0.130-1.el8_102026-08-13redhat
redhatdotnet9-0-main-9.0.119-2.hum12026-07-24redhat

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

(2 across 1 ecosystem)
NuGet(2)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.Build.Tasks.Git10.0.300, 10.0.301
  • 10.0.102 up to 10.0.111: fixed in 10.0.111
  • 10.0.200 through 10.0.204: no fix on record
  • 10.0.300 up to 10.0.303: fixed in 10.0.303
—
Microsoft.SourceLink.AzureRepos.Git10.0.300, 10.0.301
  • 10.0.102 up to 10.0.111: fixed in 10.0.111
  • 10.0.200 through 10.0.204: no fix on record
  • 10.0.300 up to 10.0.303: fixed in 10.0.303
—

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 17× in last 7d / 78× 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 194 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-62900?
CVE-2026-62900 is a medium vulnerability published on August 11, 2026. Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-62900 disclosed?
CVE-2026-62900 was first published on August 11, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62900 actively exploited?
CVE-2026-62900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62900?
CVE-2026-62900 has a CVSS base score of 5.9 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-62900?
A fix for CVE-2026-62900 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62900 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62900?

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

Book a Demo →Browse All CVEs