Skip to main content

Microsoft Teams CVE-2026-65667

| EUVDEUVD-2026-54322 CRITICAL
Missing Authorization (CWE-862)
2026-08-07 secure@microsoft.com GHSA-qf3x-g8x3-rcjc
10.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Teams network endpoint
  2. Delivery
    Send request omitting authorization
  3. Exploit
    Bypass missing access check
  4. Execution
    Invoke privileged cross-scope action
  5. Impact
    Access or alter protected resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated network exploitation against Microsoft Teams, per the CVSS vector AV:N/AC:L/PR:N/UI:N (no authentication, no user interaction, low attack complexity). The only inherent limiting factor is network reachability of the vulnerable Teams service endpoint; the scope change (S:C) means successful exploitation impacts resources governed by a separate security authority. The precise feature, API, or configuration that triggers the missing authorization check is not detailed in the available data and should be confirmed via the MSRC advisory.

Impact

The signals are strongly aligned toward high priority: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H) describes network-reachable, low-complexity, unauthenticated exploitation with no user interaction and a scope change, yielding the maximum 10.0 base score. Against that, the exploitation-likelihood signals are quiet - the vulnerability is not in CISA KEV and no public POC or exploit code was provided, so there is no evidence of active exploitation and (no EPSS value was supplied to quantify probability). This is a genuine priority driven by ease and impact of exploitation rather than by observed in-the-wild activity; the absence of KEV/POC data reflects analysis-time intelligence, not a guarantee the flaw is hard to weaponize. One caveat: the description characterizes the outcome as 'elevate privileges' while the CVSS impact is scored as confidentiality/integrity with no availability effect and a scope change - verify with the MSRC advisory whether this is an authorization-bypass leading to cross-tenant/cross-user access versus a classic role escalation.

Exploit ScenarioDerived

A remote attacker with network access to the Teams service sends a crafted request to an API or action that fails to verify authorization, invoking functionality reserved for a privileged role or another tenant/user. Because no authentication, user interaction, or special complexity is required and scope is changed, the attacker gains high-impact read/modify access to resources outside the originally exposed component. No public exploit code is identified at time of analysis.

Monitor Track and reassess. Why: Vendor states no customer action required.
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 07, 2026

Privilege elevation in Microsoft Teams lets a remote, unauthenticated attacker gain unauthorized access across a network due to a missing authorization check (CWE-862). The maximum 10.0 CVSS rating stems from a changed scope with high confidentiality and integrity impact, meaning the flaw reaches resources beyond the initially vulnerable component. No public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the perfect-score, no-precondition profile makes it a top-tier patch priority.

RemediationAI

Consult the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-65667 for the authoritative fix and servicing status; for cloud-serviced Teams components Microsoft typically deploys the correction on the service side with no customer action required, while any client-side updates should be applied by ensuring Teams desktop/mobile clients auto-update to the latest build. Patch available per vendor advisory (exact fixed version not specified in the provided data - do not assume a build number). As interim risk reduction pending confirmation of the fix scope, restrict Teams exposure to trusted, authenticated Entra ID identities, enforce Conditional Access and MFA, review external/guest access and federation settings, and monitor Teams and Microsoft 365 audit logs for anomalous privileged actions; note these controls reduce but may not fully eliminate a server-side authorization bypass, so confirming Microsoft's remediation is the primary control.

Affected VersionsENISA

Microsoft Teams - (version not specified)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Microsoft Teams is Microsoft's collaboration and communication platform, delivered as a cloud service integrated with Microsoft 365/Entra ID and consumed through web, desktop, and mobile clients. The root cause is CWE-862 (Missing Authorization): a code path that performs a sensitive action without verifying that the requesting principal is entitled to perform it, allowing an actor to invoke privileged functionality reserved for higher-trust roles. Because the CVSS vector marks scope as changed (S:C), the authorization gap in the vulnerable Teams component grants access to resources managed by a separate security authority - consistent with a service-side authorization bypass rather than a local client bug. No CPE strings were supplied, so exact affected build identifiers are not enumerable from the provided data; the single MSRC reference indicates this is a Microsoft-serviced (likely cloud-fixed) vulnerability.

Know when Teams gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
ENISA EUVD CRITICAL
vuln.today AI 10.0 CRITICAL

Missing authorization is network-reachable and unauthenticated with no user interaction (AV:N/AC:L/PR:N/UI:N); scope changes across security authorities (S:C) with high C/I and no availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

Missing authorization in Microsoft Teams allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

CVE-2026-65667 is a critical, unauthenticated privilege escalation vulnerability in Microsoft Teams (CVSS 10.0) that exposes all organizational users and connected corporate resources to unauthorized access and control. An attacker requires no credentials or user interaction to exploit this flaw, potentially gaining elevated permissions across Teams infrastructure and integrated systems. With no vendor patch currently released, immediate defensive actions are essential to prevent organizational compromise.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: network segmentation isolating Teams infrastructure from critical systems; enforcement of least-privilege access for Teams administration; real-time monitoring and alerting for unauthorized access patterns and privilege escalation attempts; regular audit and restriction of Teams app permissions and integrations; and establishment of alternative communication channels for sensitive organizational communications pending patch availability.

Threat Intelligence Overview

EPSS Score
0.5%
Top 63% exploitable
Prevalence
High
Microsoft 365 collaboration platform used across most enterprise environments
EU Gov Alert
Listed
Top-tier national CERT alert
Threat Intel
2
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:N/A
Service Type
Hosted
Vendor-managed, no client patch needed
Data Quality
8 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat Yes
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

70
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +20

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Related Vulnerabilities in Microsoft Teams Authentication and Authorization Flaws

View all 3

More in Teams

View all
CVE-2026-65768 CRITICAL
9.8 Aug 11

Path-traversal-driven remote code execution affects the Microsoft Teams client for Android in all builds prior to 1.0.0.

CVE-2024-42004 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti

CVE-2024-41145 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27

CVE-2024-41138 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work

CVE-2023-4863 HIGH POC
8.8 Sep 12

Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to

CVE-2026-65767 HIGH
7.6 Aug 11

Cross-site scripting in Microsoft Teams for Android (versions below 1.0.76.202611302) enables an authenticated attacker

CVE-2020-10146 MEDIUM POC
5.4 Dec 09

The Microsoft Teams online service contains a stored cross-site scripting vulnerability in the displayName parameter tha

CVE-2023-29330 HIGH
8.8 Aug 08

Microsoft Teams Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely expl

CVE-2023-29328 HIGH
8.8 Aug 08

Microsoft Teams Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely expl

CVE-2026-42835 HIGH
8.1 Jun 09

Information disclosure in Microsoft Teams for Android allows an authenticated remote attacker to extract sensitive data

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy