CVE-2026-48582

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-19. A secondary CVSS source baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-38090 (ENISA EUVD) · GHSA-j97v-rpjv-q4wf (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.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).

Missing authorization in Microsoft Exchange Online allows an authorized attacker to elevate privileges over a network.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 19, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-48582

Vendor Advisories for CVE-2026-48582(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 27× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 805 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 705 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48582?
CVE-2026-48582 is a critical-severity vulnerability; its CVE record was published on June 19, 2026. Missing authorization in Microsoft Exchange Online allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-48582 made public?
CVE-2026-48582 was made public on June 18, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on June 19, 2026. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-48582 actively exploited?
CVE-2026-48582 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48582?
CVE-2026-48582 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48582?
A fix for CVE-2026-48582 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-48582 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48582?

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