CVE-2026-69315

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

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

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

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

Exposure of sensitive system information to an unauthorized control sphere in Windows License Manager allows an authorized attacker to disclose information locally.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 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-69315

Vendor Advisories for CVE-2026-69315(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 34× in last 7d / 64× 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-09-18 21:04 UTCEG score recompute
  2. 2026-09-18 21:04 UTCVendor advisory
  3. 2026-09-18 21:03 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 14:11 UTCVendor advisory
  6. 2026-09-18 14:11 UTCGHSA enrichment
  7. 2026-09-17 23:42 UTCVendor advisory
  8. 2026-09-17 23:42 UTCGHSA enrichment
  9. 2026-09-17 20:11 UTCEG score recompute
  10. 2026-09-17 20:11 UTCVendor advisory
  11. 2026-09-17 20:11 UTCGHSA enrichment
  12. 2026-09-17 16:03 UTCEG score recompute
  13. 2026-09-17 16:03 UTCVendor advisory
  14. 2026-09-17 16:03 UTCGHSA enrichment
  15. 2026-09-16 22:02 UTCEG score recompute
  16. 2026-09-16 22:02 UTCVendor advisory
  17. 2026-09-16 22:02 UTCGHSA enrichment
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 23:05 UTCVendor advisory
  21. 2026-09-15 23:05 UTCGHSA enrichment
  22. 2026-09-15 17:56 UTCEG score recompute
  23. 2026-09-15 17:56 UTCVendor advisory
  24. 2026-09-15 17:56 UTCGHSA enrichment
  25. 2026-09-14 23:15 UTCVendor advisory
Show 39 more
  1. 2026-09-14 23:15 UTCGHSA enrichment
  2. 2026-09-14 17:46 UTCVendor advisory
  3. 2026-09-14 17:46 UTCGHSA enrichment
  4. 2026-09-13 23:59 UTCEG score recompute
  5. 2026-09-13 23:59 UTCVendor advisory
  6. 2026-09-13 23:59 UTCGHSA enrichment
  7. 2026-09-12 23:28 UTCEG score recompute
  8. 2026-09-12 23:28 UTCVendor advisory
  9. 2026-09-12 23:28 UTCGHSA enrichment
  10. 2026-09-11 22:56 UTCVendor advisory
  11. 2026-09-11 22:56 UTCGHSA enrichment
  12. 2026-09-11 20:05 UTCVendor advisory
  13. 2026-09-11 20:05 UTCGHSA enrichment
  14. 2026-09-11 17:01 UTCEG score recompute
  15. 2026-09-11 17:01 UTCVendor advisory
  16. 2026-09-11 17:01 UTCGHSA enrichment
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 09:37 UTCEPSS rescore
  19. 2026-09-10 23:35 UTCGHSA enrichment
  20. 2026-09-10 22:38 UTCEG score recompute
  21. 2026-09-10 22:38 UTCGHSA enrichment
  22. 2026-09-09 22:06 UTCGHSA enrichment
  23. 2026-09-09 20:06 UTCVendor advisory
  24. 2026-09-09 20:06 UTCGHSA enrichment
  25. 2026-09-09 00:06 UTCEG score recompute
  26. 2026-09-09 00:06 UTCVendor advisory
  27. 2026-09-09 00:06 UTCGHSA enrichment
  28. 2026-09-08 21:49 UTCEG score recompute
  29. 2026-09-08 21:49 UTCVendor advisory
  30. 2026-09-08 21:48 UTCGHSA enrichment
  31. 2026-09-08 20:30 UTCEG score recompute
  32. 2026-09-08 20:30 UTCGHSA enrichment
  33. 2026-09-08 19:42 UTCEG score recompute
  34. 2026-09-08 19:42 UTCGHSA enrichment
  35. 2026-09-08 18:55 UTCEG score recompute
  36. 2026-09-08 18:55 UTCGHSA enrichment
  37. 2026-09-08 17:53 UTCEG score recompute
  38. 2026-09-08 17:53 UTCVendor advisory
  39. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69315?
CVE-2026-69315 is a medium vulnerability published on September 8, 2026. Exposure of sensitive system information to an unauthorized control sphere in Windows License Manager allows an authorized attacker to disclose information locally.
When was CVE-2026-69315 disclosed?
CVE-2026-69315 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69315 actively exploited?
CVE-2026-69315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-69315?
CVE-2026-69315 has a CVSS v4.0 base score of 5.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69315?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69315, 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-69315

Explore →

Is Your Infrastructure Affected by CVE-2026-69315?

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

Start Free Scan →Browse All CVEs