Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Copilot Business Chat over network
-
ExploitSubmit crafted input with special elements
-
ExecutionTrigger command injection in backend processing
-
ImpactCopilot discloses out-of-scope information
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be able to supply input that Microsoft 365 Copilot Business Chat processes - i.e. the target organization must have Copilot Business Chat (the enterprise 'work' grounded chat) enabled and reachable. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no user interaction, and low complexity against the service as deployed by Microsoft. The injection depends on the service failing to neutralize special elements in attacker-supplied content; the scope change (S:C) implies the disclosed data crosses into a context beyond the attacker's own. Limiting factors: the product is a Microsoft-hosted SaaS, so exploitation and remediation are tied to Microsoft's cloud configuration rather than a customer-installed version, and organizations that have not enabled Copilot Business Chat are not exposed. CISA SSVC marks exploitation as non-automatable, suggesting it is not trivially mass-exploitable. |
| Impact | Signals are moderately conflicting and point to a real-but-not-urgent priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N, base 8.6) describes a network-reachable, unauthenticated, low-complexity flaw with a scope change and HIGH confidentiality impact but NO integrity or availability impact - i.e. an information-disclosure issue, not code execution, despite the CWE-77/command-injection labeling. This CVSS-vs-description tension should be verified with Microsoft: the title says 'command injection' yet I:N/A:N indicate the attacker reads data rather than altering state or running arbitrary commands with persistence. The remaining signals temper the high base score: EPSS is only 0.49% (41st percentile), the vulnerability is NOT in CISA KEV, and CISA SSVC records Exploitation=none, Automatable=no, Technical Impact=partial. The low EPSS and non-automatable SSVC are consistent with each other and suggest no widespread opportunistic exploitation is expected. Because the affected product is a Microsoft-operated SaaS (Microsoft 365 Copilot), remediation is largely vendor-side cloud mitigation rather than customer patching, which further lowers operational urgency for most defenders. Net: treat as a standard-priority confidentiality issue to track, not a drop-everything emergency - but confirm the actual technical impact and command-injection semantics directly with the MSRC advisory. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker crafts malicious input (e.g. content or a prompt processed by Microsoft 365 Copilot Business Chat) containing improperly neutralized special elements that the backend interprets as a command, causing Copilot to return or leak information the attacker should not be able to access. Because the CVSS scope is Changed, the disclosed data may belong to a different security context (e.g. another user or component) than the one the attacker controls. No public exploit code has been identified, and CISA SSVC rates exploitation as none and non-automatable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 07, 2026
Unauthenticated command injection (CWE-77) in Microsoft 365 Copilot's Business Chat allows an attacker who can supply content the service processes to disclose information, with the scope-change flag indicating the exposed data crosses out of the attacker's own context. The affected component is the enterprise 'work'-grounded Copilot chat (CPE microsoft:365_copilot_chat), delivered as a Microsoft-hosted SaaS rather than a customer-installed binary, so only organizations that have Copilot Business Chat enabled and reachable are exposed. Exploitation is not confirmed: no public exploit code exists at time of analysis, the CVE is not in CISA KEV, EPSS is a low 0.49% (41st percentile), and CISA SSVC marks exploitation as none and non-automatable - making this a real but moderate-priority issue rather than an urgent one, even though the CVSS base score is 8.6.
Earlier versions of this analysis (1)
Information disclosure in Microsoft 365 Copilot Business Chat (BizChat/M365 Chat) allows an unauthenticated remote attacker to cause the assistant to surface data the victim can access but the attacker cannot, by getting the victim to invoke Copilot over attacker-influenced content such as email, documents, or files already present in the tenant. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N, 7.4) classifies this as a confidentiality-only, scope-changing issue that cannot be triggered without victim interaction, meaning the attacker sets up the content and waits for a user to prompt Copilot against it. Exploitation status: no public exploit identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); because Copilot Business Chat is a Microsoft-hosted service, exposure is bounded to the window before Microsoft's server-side remediation rather than to any customer-managed patch cycle.
RemediationAI
Because Microsoft 365 Copilot Business Chat is a Microsoft-hosted cloud service, the corrective fix is delivered server-side by Microsoft rather than installed by customers; the authoritative source for current status and any required action is the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-78501 (Patch available per vendor advisory; no exact customer-installable fix version applies to a SaaS component). Administrators should confirm with Microsoft's advisory whether any tenant-side configuration change is required, and should treat the primary compensating control as exposure reduction: if Copilot Business Chat is not a business requirement, disable or do not enable it, since organizations without the service enabled and reachable are not exposed - the trade-off is loss of the assistant's grounded-chat functionality for users. Where the service must remain enabled, restrict its availability to the minimum set of licensed users and business units through Microsoft 365 admin licensing and Copilot deployment policies, which narrows the reachable attack surface at the cost of reduced productivity coverage and potential user friction. Additionally, monitor Copilot and Microsoft 365 audit/usage logs for anomalous or unexpected query patterns that could indicate injected input being processed, accepting that this is detective rather than preventive and will not stop a successful disclosure. Note that no public exploit code and no known active exploitation have been identified at time of analysis (SSVC Exploitation: none; non-automatable), and EPSS is only 0.49%, so these measures should be sequenced as measured risk reduction rather than emergency response.
Affected VersionsENISA
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
The root cause class is CWE-77, improper neutralization of special elements used in a command, which in a Microsoft 365 Copilot Business Chat context means attacker-influenced input is passed into a command-handling path without adequate sanitization or escaping. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N describes a network-reachable flaw exploitable with low complexity, no authentication (PR:N) and no user interaction (UI:N), which is consistent with a cloud-hosted conversational service that accepts requests directly. The scope-changed (S:C) component, combined with confidentiality-high and no integrity or availability impact, indicates a read-only disclosure of data belonging to a security authority beyond the attacker's own context - that is, injected commands can surface information the requester should not see, without altering or disrupting the service. Because the product is the Microsoft-operated Business Chat surface (CPE cpe:2.3:a:microsoft:365_copilot_chat), the version field is unversioned in EUVD and the attack surface is the hosted service as Microsoft deploys it; the practical consequence is that exposure and remediation are governed by Microsoft's cloud configuration and tenant enablement rather than by any customer-side package version. CISA's SSVC assessment (Exploitation: none, Automatable: no, Technical Impact: partial) further indicates the injection is not trivially scriptable for mass abuse.
Know when 365 Copilot Chat 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
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Network-reachable, unauthenticated (PR:N), no user interaction, low complexity; confidentiality-only disclosure with a scope change to another context, so C:H and I:N/A:N.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
Improper neutralization of special elements used in a command ('command injection') in Microsoft 365 Copilot's Business Chat allows an unauthorized attacker to disclose information over a network.
Executive ViewAI
Microsoft 365 Copilot Business Chat, an AI assistant used for enterprise work, contains a command injection vulnerability that could allow unauthorized access to sensitive information beyond the attacker's own context. Organizations with this feature enabled are exposed, though no public exploit has been identified at time of analysis, and the overall risk is moderate. Leadership should prioritize confirming exposure and implementing interim mitigations while awaiting a vendor patch.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling Microsoft 365 Copilot Business Chat where not business-critical, restricting access to authorized users, enforcing least privilege, monitoring for unusual data access patterns, and applying network segmentation to limit exposure.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
More in 365 Copilot Chat
View allCrafted command input submitted to Microsoft 365 Copilot Chat can cause the hardened service to disclose sensitive infor
Improper neutralization of special elements (CWE-77 command injection) in Microsoft 365 Copilot Chat allows an unauthent
Microsoft 365 Copilot BizChat Information Disclosure Vulnerability. Rated high severity (CVSS 8.2), this vulnerability i
Microsoft 365 Copilot BizChat Information Disclosure Vulnerability. Rated medium severity (CVSS 6.5), this vulnerability
EUVD-2026-82590
GHSA-hjj2-64g6-jw5p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB