← Blog

Microsoft fixed the Copilot flaw. What it could reach is still up to you.

Tenant Strike2 min read

A one-click Copilot flaw could have pulled mail and files from Microsoft 365. Microsoft patched it, with nothing for customers to do. The lesson for a small business is about permissions.

This summer, researchers at Varonis showed that one click on a crafted link could make Microsoft 365 Copilot leak data. The flaw, called SearchLeak (CVE-2026-42824), could reach mailbox, calendar, OneDrive and SharePoint data.

There's no need to panic about this one. Microsoft fixed it on its side in early June, before the research was published, and customers didn't have to do anything. No real-world attacks were found. A similar flaw in the consumer version of Copilot was fixed in August.

So why bring it up now? Because there will be another one, and there's a part of this that Microsoft can't fix for you.

The flaw is Microsoft's. The reach is yours.

Copilot works on behalf of the person using it. It can only get to what that person can already open. So when something goes wrong, what's exposed depends on how much that one employee could reach in the first place.

If a sales rep can open the payroll folder because someone shared it with everyone in 2021, that folder is within reach of anything acting as that rep. That's true of a flawed AI tool, and of an attacker with the rep's password.

This matters more now that Copilot is part of Microsoft's standard small-business plans. That post covers the test to run before you switch it on. This one covers the settings underneath.

Three settings to look at this week

What kind of link people get by default. When someone shares a file, what does SharePoint offer first? If it's a link anyone can use, change it. Links limited to specific people should be the default, and view-only is a better starting point than edit.

Whether anonymous links ever expire. If your company allows "anyone" links at all, set an expiration. Otherwise a link sent in 2021 can still work today.

Who outside the company still has access. Look through your guest accounts and remove the ones tied to finished projects and former vendors.

It's also worth one sentence to your team: use the Copilot in your work account for work data, not a personal one. The consumer and business products aren't the same, and the August flaw only affected the consumer version.

What a settings check won't tell you

These are company-wide settings. They close off the easy paths, but they won't tell you whether one specific folder is shared too widely. For that, run the test in our earlier post, or use Microsoft's SharePoint reports.

Tenant Strike reads the settings side for you: sharing defaults, anonymous link expiry and stale guests, along with the rest of your Microsoft 365 setup.

AI-researched from public sources. We label AI-assisted writing — see our trust page.

See your own risk

Want this for your own Microsoft cloud?

Tenant Strike finds the security gaps in your Microsoft 365 and Azure, shows how they chain into a real break-in, and hands you a step-by-step fix for every one — read-only. The scanner never requests a write permission. The optional configuration reader holds one, ConfigurationMonitoring.ReadWrite.All, whose only writes are Microsoft’s own snapshot records; it cannot change your tenant. Start a 7-day Pro trial — no credit card.