CVE-2026-69519

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-21. The CNA's CVSS baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.6EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Observable response discrepancy in Azure Stack HCI allows an unauthorized attacker to disclose information over a network.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
54
EG Risk 54/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
Severity86% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (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 20, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
microsoftMentions a patch (unverified)

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-69519

Vendor Advisories for CVE-2026-69519(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 32× in last 7d / 158× 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 304 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-69519?
CVE-2026-69519 is a high vulnerability published on August 20, 2026. Observable response discrepancy in Azure Stack HCI allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-69519 disclosed?
CVE-2026-69519 was first published on August 20, 2026, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69519 actively exploited?
CVE-2026-69519 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69519?
CVE-2026-69519 has a CVSS base score of 8.6 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-69519?
A fix for CVE-2026-69519 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-69519 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-69519

Explore →

Is Your Infrastructure Affected by CVE-2026-69519?

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