CVE-2026-41106
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 · uneditedUrl redirection to untrusted site ('open redirect') in M365 Copilot allows an unauthorized attacker to elevate privileges over a network.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceOpen redirect vulnerability in M365 Copilot enables unauthorized attackers to redirect users to malicious sites, which can be chained with other techniques to elevate privileges over a network. The high CVSS score of 9.3 indicates the redirect can be leveraged to bypass authentication or session controls.
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 dataall versionsCVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm M365 Copilot is enabled in your tenantSign in to Microsoft 365 admin center, navigate to Settings > Services & add-ins, or use Microsoft Entra admin center to check for Copilot license assignments and enabled featuresAffected if Copilot is actively enabled for any user in the organization
-
Review Copilot activity logs for suspicious redirect patternsAccess Microsoft 365 Purview compliance portal or Exchange admin center audit logs. Search for Copilot-related entries and examine URL parameters in request payloads for unexpected external domainsAffected if Log entries show Copilot-generated URLs redirecting to non-Microsoft domains, especially those not in your allowed list
-
Check network proxy/DNS logs for Copilot-initiated connections to untrusted domainsQuery your network firewall, proxy, or DNS logging system for outbound connections originating from Copilot client IPs or service endpoints connecting to suspicious or unknown external domainsAffected if Network logs reveal Copilot creating connections to unfamiliar or potentially malicious external URLs
-
Inspect user-reported Copilot interactions for abnormal URL behaviorCollect and review any user complaints or IT tickets mentioning Copilot displaying unexpected links, redirect warnings, or URLs that do not match expected Microsoft domains (microsoft.com, copilot.microsoft.com)Affected if Users report being redirected to domains outside the Microsoft trusted domain list during Copilot sessions
-
Audit conditional access and application policies for CopilotNavigate to Microsoft Entra ID > Security > Conditional Access and review policies targeting Copilot. Check if policies exist to restrict redirect destinations or validate URL targetsAffected if No policies are configured to validate or restrict Copilot redirect destinations, leaving the open redirect path unmitigated at the identity layer
Your organization is affected if M365 Copilot is enabled and no network-level or conditional access controls exist to detect or block suspicious redirect destinations.
Generated from the published advisory. Verify against your own configuration.
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 dataUntil Microsoft releases a patch, implement network-level controls to restrict outgoing connections from Copilot to untrusted domains and monitor for suspicious redirect patterns in logs. Apply principle of least privilege to Copilot permissions.
- Consultation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41106 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41106 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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