Skip to content
Applications

CVE-2026-59864

9.3
Critical
EPSS 1%Patch availableJul 17, 2026

Kiota plugin generator path traversal allows file inclusion in Teams/Copilot plugin manifests

common questions

Is CVE-2026-59864 being exploited?

Not confirmed. CVE-2026-59864 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.3% probability of exploitation in the next 30 days.

How severe is CVE-2026-59864?

CVE-2026-59864 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59864?

Yes. A fix has been recorded for CVE-2026-59864. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59864 affect?

CVE-2026-59864 affects Kiota < 1.32.5, kiota plugin add, kiota plugin generate -t APIPlugin, Generated Microsoft 365 Copilot plugins, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59864?

Upgrade Kiota to >=1.32.5 and sanitize/validate template file paths in build pipelines.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Kiota < 1.32.5kiota plugin addkiota plugin generate -t APIPluginGenerated Microsoft 365 Copilot pluginsMicrosoft Teams plugin manifests
impact

Path traversal in template.file permits inclusion of arbitrary/out-of-package files in generated Teams/Copilot plugins, enabling data disclosure or malicious code when deployed.

action required

Patch when possible

affected versions
microsoft kiota
  • affected>= 1.30.0 and < 1.31.1
  • affected< 1.29.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free