CVE-2026-48567

CRITICALNVD 9.810.0▲
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-05. NVD baseline CVSS 9.8; sources differ by 0.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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

Authentication bypass by spoofing in Azure HorizonDB allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
9.8
EG Score
10.0(medium)
EG Risk
60(Track)
EG Risk 60/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
Severity100% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
62%
KEV
Not listed

Published

June 4, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Sep 16, 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-48567

Vendor Advisories for CVE-2026-48567(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 9× in last 7d / 67× 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 640 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48567?
CVE-2026-48567 is a critical vulnerability published on June 4, 2026. Authentication bypass by spoofing in Azure HorizonDB allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-48567 disclosed?
CVE-2026-48567 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48567 actively exploited?
CVE-2026-48567 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 38.0% of all scored CVEs.
What is the CVSS score of CVE-2026-48567?
CVE-2026-48567 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 10.0.
How do I remediate CVE-2026-48567?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48567, 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-48567

Explore →

Is Your Infrastructure Affected by CVE-2026-48567?

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

Start Free Scan →Browse All CVEs