CVE-2026-69502

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 10.0Exploit: 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).

Server-side request forgery (ssrf) in Azure SQL Database allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/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
Severity100% × 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
0.8%
EPSS %ILE
55th
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 total (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 21, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 8, 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-69502

Vendor Advisories for CVE-2026-69502(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 60× in last 7d / 318× 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 585 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69502?
CVE-2026-69502 is a critical vulnerability published on August 21, 2026. Server-side request forgery (ssrf) in Azure SQL Database allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-69502 disclosed?
CVE-2026-69502 was first published on August 21, 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-69502 actively exploited?
CVE-2026-69502 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69502?
CVE-2026-69502 has a CVSS base score of 10.0 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-69502?
A fix for CVE-2026-69502 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-69502 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-69502?

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

Book a Demo →Browse All CVEs