Skip to content
Applications

CVE-2026-59865

9.3
Critical
EPSS 4%Patch availableJul 17, 2026

Command injection in Kiota 'kiota info' allows execution of attacker-supplied commands.

common questions

Is CVE-2026-59865 being exploited?

Not confirmed. CVE-2026-59865 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 4.4% probability of exploitation in the next 30 days.

How severe is CVE-2026-59865?

CVE-2026-59865 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-59865?

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

What does CVE-2026-59865 affect?

CVE-2026-59865 affects Kiota < 1.32.5, Kiota VS Code extension (dependency-install flow), Developer machines processing untrusted OpenAPI specs, CI/CD jobs running kiota info. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59865?

Upgrade Kiota to 1.32.5 and avoid running install commands from untrusted specs

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 VS Code extension (dependency-install flow)Developer machines processing untrusted OpenAPI specsCI/CD jobs running kiota info
impact

Attacker-controlled OpenAPI spec can inject shell commands via kiota info or VS Code dependency-install, enabling arbitrary command execution on dev machines/CI.

action required

Immediate action required

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