CVE-2026-65667

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory

Also known asEUVD-2026-54322 (ENISA EUVD) · GHSA-qf3x-g8x3-rcjc (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 10.0Exploit: 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 Teams allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
57th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 6, 2026

Last Modified

November 19, 2026

Advisory Details (1)

Auto-updated Nov 19, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

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

Vendor and National Authority Advisories for CVE-2026-65667(3)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 83× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 886 rows 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 786 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-65667?
CVE-2026-65667 is a critical-severity vulnerability; its CVE record was published on August 6, 2026. Missing authorization in Microsoft Teams allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-65667 made public?
CVE-2026-65667 was made public on August 6, 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 August 6, 2026. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-65667 actively exploited?
CVE-2026-65667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65667?
CVE-2026-65667 has a CVSS base score of 10.0 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-65667?
A fix for CVE-2026-65667 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-65667 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-65667 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65667?

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