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 57% 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
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
44%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 20, 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(12)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-8.0 (8.0.130-0ubuntu1~24.04.1) @ noble2026-08-20ubuntu
redhatdotnet10.0-0:10.0.111-1.el10_22026-08-17redhat
redhatdotnet9.0-0:9.0.120-1.el9_82026-08-17redhat
redhatdotnet10.0-0:10.0.111-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.

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 41× in last 7d / 66× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:02 UTCVendor advisory
  3. 2026-08-20 16:43 UTCVendor advisory
  4. 2026-08-20 15:02 UTCVendor advisory
  5. 2026-08-20 14:13 UTCVendor advisory
  6. 2026-08-19 21:15 UTCVendor advisory
  7. 2026-08-19 17:47 UTCEG score recompute
  8. 2026-08-19 17:47 UTCVendor advisory
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:51 UTCVendor advisory
  11. 2026-08-19 15:16 UTCVendor advisory
  12. 2026-08-19 14:31 UTCVendor advisory
  13. 2026-08-18 22:44 UTCVendor advisory
  14. 2026-08-18 22:13 UTCVendor advisory
  15. 2026-08-18 17:29 UTCVendor advisory
  16. 2026-08-18 13:59 UTCEG score recompute
  17. 2026-08-18 13:59 UTCVendor advisory
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 17:49 UTCVendor advisory
  20. 2026-08-17 16:20 UTCEG score recompute
  21. 2026-08-17 16:20 UTCVendor advisory
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 18:57 UTCVendor advisory
  24. 2026-08-16 18:45 UTCVendor advisory
  25. 2026-08-16 17:35 UTCVendor advisory
Show 41 more
  1. 2026-08-16 16:38 UTCEG score recompute
  2. 2026-08-16 16:38 UTCVendor advisory
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-15 20:38 UTCEG score recompute
  5. 2026-08-15 20:38 UTCVendor advisory
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 22:02 UTCVendor advisory
  8. 2026-08-14 21:18 UTCVendor advisory
  9. 2026-08-14 20:27 UTCVendor advisory
  10. 2026-08-14 18:38 UTCVendor advisory
  11. 2026-08-14 17:35 UTCVendor advisory
  12. 2026-08-14 17:09 UTCVendor advisory
  13. 2026-08-14 16:28 UTCEG score recompute
  14. 2026-08-14 16:28 UTCVendor advisory
  15. 2026-08-14 14:07 UTCEG score recompute
  16. 2026-08-14 14:07 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 17:35 UTCVendor advisory
  19. 2026-08-13 16:32 UTCVendor advisory
  20. 2026-08-12 18:15 UTCVendor advisory
  21. 2026-08-12 15:22 UTCEG score recompute
  22. 2026-08-12 15:22 UTCVendor advisory
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-12 00:20 UTCVendor advisory
  25. 2026-08-11 23:42 UTCVendor advisory
  26. 2026-08-11 22:45 UTCVendor advisory
  27. 2026-08-11 22:10 UTCEG score recompute
  28. 2026-08-11 22:10 UTCVendor advisory
  29. 2026-08-11 21:19 UTCEG score recompute
  30. 2026-08-11 21:19 UTCVendor advisory
  31. 2026-08-11 19:35 UTCEG score recompute
  32. 2026-08-11 19:35 UTCVendor advisory
  33. 2026-08-11 19:00 UTCEG score recompute
  34. 2026-08-11 19:00 UTCVendor advisory
  35. 2026-08-11 18:13 UTCEG score recompute
  36. 2026-08-11 18:13 UTCVendor advisory
  37. 2026-08-11 17:41 UTCEG score recompute
  38. 2026-08-11 17:41 UTCVendor advisory
  39. 2026-08-11 17:16 UTCEG score recompute
  40. 2026-08-11 17:16 UTCVendor advisory
  41. 2026-08-11 17:11 UTCMITRE cvelistV5first tracked

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 August 20, 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 56.5% 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

Explore the affected products and dependency analysis for 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