# CVE-2025-32711: M365 Copilot Information Disclosure Vulnerability

> An AI command injection flaw in Microsoft 365 Copilot allows unauthorized attackers to disclose sensitive information over the network.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-h2w9-p5qf-qmrh

## What is CVE-2025-32711?

CVE-2025-32711 is a critical code injection vulnerability in Microsoft 365 Copilot, published on 11 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ai command injection in M365 Copilot allows an unauthorized attacker to disclose information over a network.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-32711?

It affects 1 product.


Products: Microsoft 365 Copilot.

## How do I fix CVE-2025-32711?

No fix has been published for CVE-2025-32711 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32711 being exploited?

There is no known exploitation of CVE-2025-32711 in the wild and no public exploit code.

Public exploit code:

- Scan LLM outputs and AI-generated content for data exfiltration signals (EchoLeak, CVE-2025-32711) before they reach users or downstream systems (github_poc): https://github.com/vikasudasi/exfil-scan
- Proof-of-concept and analysis for CVE-2025-32711 (github_poc): https://github.com/daryllundy/cve-2025-32711
- Black-box test whether an LLM chatbot is vulnerable to markdown/HTML exfil (CVE-2025-32711 class). Spins up a sink, sends payloads, renders in headless Chromium, correlates via network. (github_poc): https://github.com/TreRB/markdown-exfil-tester
- AISec Plus Week 1 threat write-up — EchoLeak (CVE-2025-32711), zero-click indirect prompt injection in Microsoft 365 Copilot. (github_poc): https://github.com/Danielossai12/aisecplus-week01-danielossai
- Threat hunt reconstructing an M365 Copilot indirect prompt injection (CVE-2025-32711 "EchoLeak"): poisoned email attachment, Graph API data collection, markdown-image exfiltration, and system prompt leakage. Sentinel + KQL across Office, Copilot and Entra telemetry. 17/17 flags. (github_poc): https://github.com/Danielle-Respes/Threat-Hunt-EchoLeak-Copilot-Prompt-Injection-Sentinel-KQL-Oct-2026

## Other vulnerabilities in Microsoft 365 Copilot

- [CVE-2026-85885](https://insights.sbomify.com/CVE-2026-85885/): Microsoft 365 Copilot Elevation of Privilege Vulnerability (critical 9.9)
- [CVE-2026-50517](https://insights.sbomify.com/CVE-2026-50517/): Microsoft M365 Copilot Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2026-54130](https://insights.sbomify.com/CVE-2026-54130/): M365 Copilot Information Disclosure Vulnerability (critical 9.8)
- [CVE-2025-60724](https://insights.sbomify.com/CVE-2025-60724/): GDI+ Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2025-53766](https://insights.sbomify.com/CVE-2025-53766/): GDI+ Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32711 and fix it if it is affected.

What it is: CVE-2025-32711 is a critical code injection vulnerability in Microsoft 365 Copilot, published on 11 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32711 in the wild and no public exploit code.

Affected product: Microsoft 365 Copilot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32711/ (Markdown: https://insights.sbomify.com/CVE-2025-32711/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32711
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32711
- OSV: https://osv.dev/vulnerability/CVE-2025-32711

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32711/
Summaries are generated and may contain mistakes; the official description above is the record.