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.5%, top 55% 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 — 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: 1%CVSS: 5.9Exploit: None knownExposed: 0

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.9(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 16, 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 / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.111-10.0.11-0ubuntu1~26.04.1) @ resolute2026-09-18ubuntu
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
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.el10_02026-08-24redhat
redhatdotnet10.0-0:10.0.111-1.el9_82026-08-17redhat
redhatdotnet9.0-0:9.0.120-1.el9_82026-08-17redhat
redhatdotnet10.0-0:10.0.111-1.el10_22026-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 rangeFixed inDependents
Microsoft.Build.Tasks.Git10.0.300, 10.0.30110.0.303—
Microsoft.SourceLink.AzureRepos.Git10.0.300, 10.0.30110.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 16× in last 7d / 95× 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 156 total refreshes for this CVE.

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

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 in the National Vulnerability Database on August 11, 2026, with the most recent update on September 16, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 55.3% of all scored CVEs.
What is the CVSS score of CVE-2026-62900?
CVE-2026-62900 has a CVSS v4.0 base score of 5.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62900?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62900, 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-62900

Explore →

Is Your Infrastructure Affected by CVE-2026-62900?

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

Start Free Scan →Browse All CVEs