Updated June 4, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Patch tracker / CVE reference / CVE-2026-42824

CVE-2026-42824

An Information Disclosure vulnerability affecting Microsoft 365 Copilot.

Risk summary

Medium

6.5

CVSS v3 base

Medium

Severity

Not listed

Actively exploited

Medium severity Microsoft vulnerability, CVSS 6.5.

Senserva AI read on CVE-2026-42824 How to fix CVE-2026-42824 Change history Admin questions

Senserva AI Opinion for CVE-2026-42824

CVE-2026-42824 is a Medium severity (CVSS 6.5) information disclosure flaw in Microsoft 365 Copilot, meaning the exposure sits inside a service that can reach across mailboxes, documents, and chats that a user has permission to see. Any tenant with Copilot licensed and enabled is potentially exposed, since the risk is that Copilot surfaces data beyond what the requesting user should retrieve. It is not in CISA KEV and has no known ransomware use, so this is a hardening priority rather than an emergency.

Do this: Confirm your tenant is on the current Copilot service build and review Copilot access scopes and sensitivity labels to limit what data it can return.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-42824

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-42824 (source: https://senserva.com/cve/CVE-2026-42824.html, data from MSRC, CISA KEV and NVD, refreshed twice a day (morning and afternoon US Central)):
- CVE-2026-42824: Medium severity Microsoft vulnerability, CVSS 6.5
- M365 Copilot Information Disclosure Vulnerability
- Actively exploited (CISA KEV): no
- Affected: Microsoft 365 Copilot
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for CVE-2026-42824

Published: 2026-06-04
Last revised: 2026-06-04
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

How to fix CVE-2026-42824

Apply the latest Microsoft security update for the affected product. Most environments deliver it automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; for a manual install, download from the Microsoft Update Catalog. The MSRC advisory lists the exact patched build per product.

Microsoft MSRC advisory NVD detail

Common questions about CVE-2026-42824

Is CVE-2026-42824 actively exploited?

It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. That can change: unexploited CVEs regularly get weaponized months after disclosure, which is why patching on your normal cadence matters.

What fixes CVE-2026-42824?

Microsoft ships the fix in its security updates. Apply the latest cumulative or security update for the affected product through Windows Update, Intune, Windows Update for Business, or the Microsoft Update Catalog, and see the MSRC advisory below for the exact build.

Which products are affected by CVE-2026-42824?

Microsoft 365 Copilot.

Can I ask my own AI about CVE-2026-42824?

Yes. This page includes a free, ready-to-paste AI prompt with CVE-2026-42824's key facts: severity, CVSS, CISA KEV status, and the affected products. Copy it into Claude, ChatGPT, or Copilot for a triage plan.

Scope and sources

Affected products

Microsoft 365 Copilot

Authoritative references

CVE record NVD detail Microsoft MSRC

Every Microsoft CVE and the patches that fix it, ranked by real-world risk: the Microsoft Patch Tracker. The full searchable CVE reference: CVE and vulnerability management.