Skip to content
major vulnerability· requires attention

Microsoft 365 is widely deployed; a remote privilege escalation in Copilot iOS can expose corporate data and impact enterprise operations.

Mobile

CVE-2026-58617

8.1
High
EPSS 0.79%Patch availableJul 15, 2026

Unauthorized privilege escalation in Microsoft 365 Copilot iOS app.

common questions

Is CVE-2026-58617 being exploited?

Not confirmed. CVE-2026-58617 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.79% probability of exploitation in the next 30 days.

How severe is CVE-2026-58617?

CVE-2026-58617 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58617?

Yes. A fix has been recorded for CVE-2026-58617. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58617 affect?

CVE-2026-58617 affects Microsoft 365 Copilot for iOS, iOS devices running Copilot, Microsoft 365 tenants using Copilot. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58617?

Apply vendor patch when released; restrict Copilot iOS use; enforce MFA and network segmentation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Microsoft 365 Copilot for iOSiOS devices running CopilotMicrosoft 365 tenants using Copilot
impact

Remote privilege escalation via network in Copilot iOS, enabling attackers to gain elevated app/tenant privileges and access or modify corporate data.

action required

Immediate action required

affected versions
Microsoft Microsoft 365 Copilot for iOS
  • affected>= 1.0 and < 2.111.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free