External risk intelligence

M365 Copilot Open Redirect Vulnerability Allows Privilege Escalation

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-41106

M365 Copilot is a widely deployed, cloud-based productivity service that is designed to be accessed by users over the internet as part of standard enterprise workflows, making its web interface and API endpoints commonly reachable in typical deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in M365 Copilot that could allow unauthorized attackers to gain elevated privileges by redirecting users to untrusted websites. This issue affects a widely used cloud-based productivity service, increasing the potential for broad impact. Understanding the nature of this threat is key to assessing its relevance to our organization.

  • Unchecked redirects can grant attacker access.
  • Critical flaw in widely used M365 Copilot.
  • Confirm relevance and exposure to M365 Copilot.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by tricking a user into clicking a specially crafted link. If the user clicks the link, it could redirect them to a malicious website, potentially leading to unauthorized access or modification of sensitive information within M365 Copilot.

  • Attacker crafts malicious link.
  • User clicks, initiating redirect.
  • Potential for unauthorized privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

A critical vulnerability in M365 Copilot could allow an unauthenticated attacker to redirect users to malicious websites, potentially leading to privilege escalation. This occurs when a user interacts with a specially crafted link.

  • User credentials and sensitive data.
  • Malicious redirection via crafted links.
  • Unauthorized access and privilege escalation.

Operational Fix

Recommended remediation, mitigation, and detection steps

This CVE affects M365 Copilot, a cloud-based productivity service. The first practical step is for the platform or security team to identify deployments, assess their reachability and criticality, and locate the accountable owner to plan remediation.

  • Platform and security teams own this issue.
  • Verify M365 Copilot reachability and criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is M365 Copilot and how is it used?

M365 Copilot is a cloud-based artificial intelligence assistant integrated into Microsoft 365 applications. It processes data across documents, emails, and meetings to generate content, summarize information, and automate tasks within enterprise workflows, effectively serving as an intelligent interface for corporate data.

What does the open redirect weakness in CVE-2026-41106 mean?

This vulnerability, classified as CWE-601, occurs when software allows an attacker to redirect a user to an external, untrusted website using a legitimate application's link. By manipulating this redirection, an attacker can trick the system into granting them unauthorized elevated privileges, essentially misusing the trust associated with the original application.

How does an attacker trigger this redirection?

The attack requires a user to interact with a specially crafted link designed to exploit the redirect mechanism. It does not trigger through automated background processes or static site visits; the exploit relies on the user actively clicking the malicious link while using the service.

Is my organization at risk from CVE-2026-41106?

Halo Surface Signal indicates that because M365 Copilot is a cloud-based service widely deployed for internet-facing enterprise tasks, its endpoints are naturally reachable in most environments. If your organization uses M365 Copilot in its standard web or API-integrated form, the service is effectively exposed to potential interaction with these crafted links.

Do I need to take action to secure M365 Copilot?

Begin by identifying the teams responsible for your M365 Copilot deployment. Work with those owners to assess the criticality of the service in your environment and monitor official update channels. Your primary focus is coordinating with the service providers or internal administrators to ensure the platform is updated according to guidance.

References