CVE-2026-105795: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in microsoft kiota
Description
### Impact When generating an API plugin manifest from an attacker-controlled or compromised OpenAPI description, Kiota copies `x-ai-capabilities.response_semantics.oauth_card_path` into the manifest without validating that it is a safe package-relative file reference. An attacker can supply parent-directory traversal, rooted paths, or absolute URIs instead of a card file within the plugin package. The unsafe reference is propagated into the generated manifest. Its security effect depends on the downstream host's handling of the reference when the plugin is packaged and deployed. This is not local code execution or a file read performed by Kiota merely during generation. A consuming host that resolves the untrusted reference can cross the intended package boundary or use an unintended authentication card. ### Affected versions The affected NuGet packages are `Microsoft.OpenApi.Kiota` and `Microsoft.OpenApi.Kiota.Builder`, starting with version 1.25.1, which introduced this manifest field. The field remains unvalidated through version 1.34.1, including the separate 1.29.1 security-backport release. Version 1.35.0 fixes the issue. ### Patches Upgrade to Kiota 1.35.0 or later and regenerate affected plugin manifests. Kiota now applies the existing safe-file-reference validator to `oauth_card_path`, drops unsafe references, and emits a warning. Valid relative card paths remain supported. - Fix: https://github.com/microsoft/kiota/pull/8055 - Fixed release: https://github.com/microsoft/kiota/releases/tag/v1.35.0 ### Workarounds Generate plugins only from trusted, integrity-protected OpenAPI descriptions. Before packaging or deployment, review generated manifests and remove any `oauth_card_path` that is not a safe relative reference confined to the plugin package. Do not rely on validation of sibling manifest fields to validate this field. ### Related advisories GHSA-4jwf-m4wg-8p66 and GHSA-p5rm-jg5c-8c77 cover `static_template.file`. Their fixes do not enforce validation at the separate `oauth_card_path` emission site.
CVSS v3.1
Score 3.1low
Affected software
microsoft
kiota
microsoft
Microsoft.OpenApi.Kiota
microsoft
Microsoft.OpenApi.Kiota.Builder
pkg:github/microsoft/kiotaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Microsoft Kiota versions >=1.25.1 and <1.35.0 copy the x-ai-capabilities.response_semantics.oauth_card_path value from potentially attacker-controlled OpenAPI descriptions into generated API plugin manifests without validating that the path is safe and package-relative. This lack of validation allows parent-directory traversal, rooted paths, or absolute URIs to be included, which can lead to a consuming host resolving references outside the intended plugin-package boundary or using unintended authentication cards. The vulnerability requires downstream resolution of the unsafe reference to have impact. The flaw is addressed in version 1.35.0.
Potential Impact
The vulnerability allows an attacker to influence the path used in the generated API plugin manifest, potentially causing the consuming host to resolve references outside the intended plugin-package boundary or to use unintended authentication cards. However, Kiota itself does not read local files or execute code during manifest generation, so exploitation depends on downstream components resolving the unsafe reference. The CVSS score is 3.1 (low severity), indicating limited impact with a requirement for user interaction and high attack complexity.
Mitigation Recommendations
Upgrade Microsoft Kiota to version 1.35.0 or later, where this path traversal vulnerability is fixed. No other mitigation actions are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-05T20:37:19.364Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac506e32cdf04f656b9a05f
Added to database: 10/06/2026, 14:34:11 UTC
Last enriched: 10/06/2026, 14:48:52 UTC
Last updated: 10/06/2026, 21:42:14 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.