CVE-2026-33823

CRITICALNVD 6.59.6
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-08. NVD baseline CVSS 6.5; sources differ by 3.1.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week

Also known asEUVD-2026-28450 (ENISA EUVD) · GHSA-w6p3-2c62-jm2g (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.5Exploit: 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).

Improper authorization in Microsoft Teams allows an authorized attacker to disclose information over a network.

CVSS v3
6.5
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
53rd
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-29). 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

May 7, 2026

Last Modified

October 26, 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-33823

Vendor Advisories for CVE-2026-33823(1)

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 26× in last 7d / 80× 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 99 of 496 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 397 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-33823?
CVE-2026-33823 is a critical-severity vulnerability; its CVE record was published on May 7, 2026. Improper authorization in Microsoft Teams allows an authorized attacker to disclose information over a network.
When was CVE-2026-33823 made public?
CVE-2026-33823 was made public on May 7, 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 May 7, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-33823 actively exploited?
CVE-2026-33823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33823?
CVE-2026-33823 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.6 (CRITICAL).
How do I remediate CVE-2026-33823?
A fix for CVE-2026-33823 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-33823 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-33823?

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