cve.bz

CVE-2026-59866 microsoft kiota: Path traversal

9.3 criticalEPSS 1.4%Fix available

Critical (9.3) in microsoft kiota. EPSS 1.4% estimated probability of exploitation activity in the next 30 days. Fixed in Microsoft.OpenApi.Kiota 1.29.1, 1.32.5.

On this page
Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.5, Kiota emitted x-ms-kiota-info clientClassName and clientNamespaceName values without identifier or path sanitization as both generated client class or namespace names and generated output path components when `kiota generate` ran without -c/--class-name, allowing an attacker-controlled or compromised OpenAPI description to write generated source outside the -o output directory and inject arbitrary text into generated class or namespace declarations. This issue is fixed in version 1.29.1 and 1.32.5 by GenerationConfiguration.SanitizeClientClassName and SanitizeClientNamespaceName.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 73rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Microsoft.OpenApi.Kiota (NuGet): fixed in 1.32.5, 1.29.1
  • Microsoft.OpenApi.Kiota.Builder (NuGet): fixed in 1.32.5, 1.29.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-59866 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59866?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59866?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59866 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
microsoft kiota>= 1.30.0, < 1.31.1
microsoft kiota< 1.29.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4vv7-jj25-4gh6NuGetMicrosoft.OpenApi.Kiota>=1.30.0 <1.32.51.32.5
GHSA-4vv7-jj25-4gh6NuGetMicrosoft.OpenApi.Kiota.Builder>=1.30.0 <1.32.51.32.5
GHSA-4vv7-jj25-4gh6NuGetMicrosoft.OpenApi.Kiota<1.29.11.29.1
GHSA-4vv7-jj25-4gh6NuGetMicrosoft.OpenApi.Kiota.Builder<1.29.11.29.1

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON