CVE-2026-26133

M365 Copilot Information Disclosure Vulnerability

HIGH
7.1
CVSS Score
Published: March 13, 2026 at 09:10 PM UTC
Updated: June 17, 2026 at 10:25 AM UTC
12 products affected across 1 vendorEdgeExcelWord

Using Microsoft 365 Copilot for Android by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft 365 Copilot for Android - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

AI command injection in M365 Copilot allows an unauthorized attacker to disclose information over a network.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 16.0.19815.10000v < 2.107.21.0 ≤ v < 16.0.19815.100001.0 ≤ v < 2.107.21.0
Affected range stops below 16.0.19815.10000, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.107.2, so it looks safe — our inference, not a vendor statement
v < 145.3800.991.0.0 ≤ v < 145.3800.991.0.0.0 ≤ v < 145.3800.991.0.0
Affected range stops below 145.3800.99, so it looks safe — our inference, not a vendor statement
v < 16.0.19822.20038v < 2.106.21.0 ≤ v < 2.106.2602061716.0.0.0 ≤ v < 16.0.19822.200381.016.0.0.0
Affected range stops below 16.0.19822.20038, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.106.26020617, so it looks safe — our inference, not a vendor statement
v < 2.1062.0.0 ≤ v < 2.106.260206172.0.0
Affected range stops below 2.106.26020617, so it looks safe — our inference, not a vendor statement
v < 16.0.19725.201421.0.0 ≤ v < 2.106.2602061716.0.1 ≤ v < 16.0.19725.201421.0.016.0.1
Affected range stops below 16.0.19725.20142, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.106.26020617, so it looks safe — our inference, not a vendor statement
v < 5.2605.01.0 ≤ v < 5.26051.0.0 ≤ v < 5.26051.01.0.0
Affected range stops below 5.2605, so it looks safe — our inference, not a vendor statement
1.0 ≤ v < 5.2605
Affected range stops below 5.2605, so it looks safe — our inference, not a vendor statement
v < 2.2.260210.212907501.0.0 ≤ v < 1.2.260302.21939102.0.0 ≤ v < 2.2.260210.212907501.0.02.0.0
Affected range stops below 1.2.260302.2193910, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.260210.21290750, so it looks safe — our inference, not a vendor statement
v < 16.0.19822.20038v < 2.106.21.0 ≤ v < 2.106.2602061716.0.0.0 ≤ v < 16.0.19822.200381.016.0.0.0
Affected range stops below 16.0.19822.20038, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.106.26020617, so it looks safe — our inference, not a vendor statement
v < 1.0.0.2026043102v < 8.3.11.0.0 ≤ v < 1.0.0.20260431022.0.0 ≤ v < 8.3.11.0.02.0.0
Affected range stops below 1.0.0.2026043102, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.3.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-77

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card