CVE-2026-24307
Microsoft 365 Copilot
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NSummary
CVE-2026-24307 is a critical-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Microsoft 365 Copilot. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as Enterprise AI Assistants; in the Privacy and Disclosure risk domain.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-24307 is an improper validation of specified type of input vulnerability, classified under CWE-1287, affecting Microsoft 365 Copilot. Published on 2026-01-22, it carries a CVSS v3.1 base score of 9.3 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N), marking it as critical due to its network accessibility, low complexity, lack of privilege requirements, and potential for high impacts on confidentiality and integrity across a changed scope.
An unauthorized attacker can exploit this vulnerability remotely over the network by tricking a user into interacting with malicious input, such as through a crafted prompt or file. Successful exploitation enables the attacker to disclose sensitive information and potentially manipulate data integrity, though it does not impact availability.
Microsoft's Security Response Center update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-24307 details the vulnerability, including recommended mitigations and available patches.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-4497
Vulnerability Data
Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information over a network.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Enterprise AI Assistants
- Risk Domain
- Privacy and Disclosure
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: m365 copilot
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.1V1.4.2V2.1.1V2.2.2
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper input type validation during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect type-validation flaws but does not prevent them during development.
Secure development lifecycle mandates input validation and type checking to prevent improper type handling.
Application security requirements explicitly include validation of input data types and formats.
Secure architecture principles promote defensive input handling and type enforcement at system boundaries.
Secure coding standards directly require proper type validation of all external inputs.