CVE-2026-73851: microsoft kiota · Path Traversal
Affects microsoft kiotaSource GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 1.29.1 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.29.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 15 Nov 2026.
What to do
Upgrade microsoft/kiota to 1.29.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmicrosoft/kiotapkg:github/microsoft/kiotaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Microsoft Kiota versions released after 1.33.0, which properly decode and validate file references to prevent path traversal. Users should upgrade to these fixed versions. Until upgrading, users should only generate clients/plugins from trusted OpenAPI descriptions and manually review generated plugin manifests to ensure that the 'response_semantics.static_template.file' field contains only simple relative paths within the expected package folder, rejecting any paths with traversal sequences, absolute paths, URIs, or percent-encoded separators.
Description
CVE-2026-73851 is a path traversal vulnerability in Microsoft Kiota affecting versions prior to 1.29.1. It allows an attacker controlling the OpenAPI description to supply crafted file references that resolve outside the intended plugin package, potentially causing unauthorized file inclusion or disclosure. Initial mitigations rejected unsafe paths based on raw strings but failed to decode percent-encoded or obfuscated inputs, allowing bypasses. Subsequent fixes decode inputs before validation and reject control characters and Unicode homoglyphs. Users should upgrade to the first release after version 1.33.0 that includes these fixes. Workarounds include generating plugins only from trusted OpenAPI descriptions and reviewing manifests for unsafe file references.
References
- github.com/microsoft/kiota/security/advisories/GHSA-p5rm-jg5c-8c77 (opens in a new tab)
- github.com/microsoft/kiota/issues/7912 (opens in a new tab)
- github.com/microsoft/kiota/pull/7910 (opens in a new tab)
- github.com/microsoft/kiota/pull/7913 (opens in a new tab)
- github.com/microsoft/kiota/commit/430008e9d700b3fe80f206c672415cfbd8e830e7 (opens in a new tab)
- github.com/microsoft/kiota/commit/de3d18d9fe31ced4ac749728d3a2f94811f59268 (opens in a new tab)
- github.com/microsoft/kiota/releases/tag/v1.29.1 (opens in a new tab)
- github.com/microsoft/kiota/releases/tag/v1.34.0 (opens in a new tab)