Skip to main content
VulnerabilityPublished Updated

CVE-2025-59272: Microsoft 365 Copilot's Business Chat · Command Injection

Affects Microsoft 365 Copilot's Business ChatSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Monitor Microsoft security advisories closely and apply patches immediately once available to remediate the vulnerability.
  2. Until patches are released, restrict or disable access to Microsoft 365 Copilot's Business Chat feature, especially for users or systems that do not require it.
  3. Implement network segmentation and access controls to limit exposure of systems running Microsoft 365 Copilot to untrusted networks or users.
  4. Employ application-layer firewalls or intrusion detection/prevention systems capable of detecting suspicious command injection patterns targeting Business Chat.
  5. Conduct thorough input validation and sanitization on any custom integrations or extensions interacting with Business Chat to prevent injection vectors.
  6. Educate users and administrators about the risks and signs of exploitation attempts related to command injection vulnerabilities.
  7. Review and audit logs for unusual command execution or access patterns that may indicate exploitation attempts.
  8. Prepare incident response plans specifically addressing potential exploitation of this vulnerability to enable rapid containment and remediation.

Description

Improper neutralization of special elements used in a command ('command injection') in Copilot allows an unauthorized attacker to perform information disclosure locally.

References

Community reviews

Loading reviews…