CVE-2026-62837

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-11. the CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Relative path traversal in Microsoft Office SharePoint allows an authorized attacker to disclose information over a network.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
30(Track)
EG Risk 30/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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 19, 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-62837

Vendor Advisories for CVE-2026-62837(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-62837?
CVE-2026-62837 is a medium vulnerability published on August 11, 2026. Relative path traversal in Microsoft Office SharePoint allows an authorized attacker to disclose information over a network.
When was CVE-2026-62837 disclosed?
CVE-2026-62837 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62837 actively exploited?
CVE-2026-62837 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 44.3% of all scored CVEs.
What is the CVSS score of CVE-2026-62837?
CVE-2026-62837 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62837?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62837, 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-62837

Explore →

Is Your Infrastructure Affected by CVE-2026-62837?

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

Start Free Scan →Browse All CVEs