CVE-2026-48567

CRITICALNVD 9.810.0▲
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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
58.3%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 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 / 163× 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 363 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 July 23, 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 58.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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