CVE-2026-58617
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 · uneditedImproper access control in Microsoft 365 Copilot for iOS allows an unauthorized attacker to elevate privileges over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced 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 confidenceThis is an improper access control vulnerability in Microsoft 365 Copilot for iOS that allows an unauthorized attacker to elevate privileges over a network. The CVSS 9.8 score indicates the vulnerability is both highly exploitable and has severe impact, likely due to missing or insufficient authorization checks in the mobile application's network interfaces or API endpoints.
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< 2.111.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Microsoft 365 Copilot for iOS is installedOpen the App Library or home screen on the iOS device and look for the Microsoft 365 Copilot app icon, or go to Settings > Apps to list installed applicationsAffected if The app is present on the device
-
Determine the installed version of Microsoft 365 CopilotOpen the App Store app, search for Microsoft 365 Copilot, tap on the app, and scroll to the Version information, or go to Settings > Microsoft 365 Copilot > Version on the deviceAffected if Cannot determine the version number
-
Compare installed version against vulnerable rangeCheck if the installed version number is less than 2.111.4 (for example, 2.111.3, 2.111.0, 2.110.0, etc.)Affected if The installed version is a number lower than 2.111.4 (e.g., 2.111.3 or earlier)
-
Verify the vulnerability requires authenticated accessUnderstand that this privilege escalation flaw affects authenticated users, meaning an attacker would need valid credentials to exploit the authorization weaknessAffected if The app handles authenticated user sessions (this is inherent to Copilot functionality)
A user is affected if Microsoft 365 Copilot for iOS is installed with a version number lower than 2.111.4, as this version range contains the improper access control vulnerability enabling privilege escalation.
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.
dbcve · scoped2.111.4
Apply vendor-provided security patches for Microsoft 365 Copilot for iOS immediately. Until patched, restrict network access to the application and monitor for anomalous authentication events.
Microsoft 365 Copilot for iOS version 2.111.4 or later
- Open the App Store on your iOS device
- Search for "Microsoft 365 Copilot" or "Copilot"
- If an update is available, tap "Update" to install version 2.111.4 or later
- Alternatively, enable automatic app updates by going to Settings > App Store > Automatic Downloads and turning on App Updates
- After updating, verify the installed version by going to the App Store, tapping your profile, and checking the app version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58617 — 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-58617 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