365 CopilotApplication · Microsoft

CVE-2026-47645

HIGH · 8.8 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Url redirection to untrusted site ('open redirect') in Microsoft 365 Copilot's Business Chat allows an unauthorized attacker to elevate privileges over a network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Open redirect vulnerability in Microsoft 365 Copilot's Business Chat component allows attackers to craft malicious URLs that redirect users to untrusted external sites. This URL redirection flaw can be chained with other techniques to perform privilege elevation attacks over a network, enabling unauthorized actors to potentially escalate their access privileges.

MitigationMonitor Microsoft's official security advisories and cumulative updates for Microsoft 365 Copilot; apply vendor-provided patches promptly. Implement URL validation and filtering at the network perimeter for Copilot-related domains until the vulnerability is remediated by Microsoft.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
365 CopilotApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Microsoft 365 Copilot deployment
    Review your Microsoft 365 admin center or Azure AD portal to list users or groups with Copilot licenses assigned. Use PowerShell with Get-MsolAccountSku or Microsoft Graph API to enumerate Copilot-enabled tenants.
    Affected if Any user or group has Microsoft 365 Copilot licenses assigned in the tenant.
  2. Identify Business Chat usage
    Check for access to the Copilot Business Chat feature, typically accessed via copilot.microsoft.com or within Microsoft 365 apps (Teams, Outlook, Office.com). Review user activity logs in Microsoft 365 admin center under Copilot usage reports.
    Affected if Business Chat component is accessible to any user in the organization.
  3. Monitor for suspicious redirect URLs
    Inspect Microsoft 365 audit logs (Search-MailboxAuditLog or Purview compliance portal) for Copilot-related sign-in events and URL patterns. Look for outbound redirects in Copilot responses using Microsoft Graph API or network proxy logs filtering for copilot.microsoft.com domains.
    Affected if Logs show HTTP 3xx responses from Copilot endpoints redirecting to external non-Microsoft domains.
  4. Review network perimeter logs
    Examine proxy, firewall, or CASB (Cloud Access Security Broker) logs for outbound connections from Copilot-associated IP addresses or user agents to untrusted external domains. Correlate with Copilot session timestamps.
    Affected if Network logs capture redirects from Copilot endpoints to domains not in your organization's allowlist.

If Microsoft 365 Copilot with Business Chat is enabled for any user in your organization, you are affected by this open redirect vulnerability since all versions are impacted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Monitor Microsoft's official security advisories and cumulative updates for Microsoft 365 Copilot; apply vendor-provided patches promptly. Implement URL validation and filtering at the network perimeter for Copilot-related domains until the vulnerability is remediated by Microsoft.

Fix this in 365 Copilot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47645 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data