Path Traversal in Microsoft.OpenApi.Kiota (CVE-2026-105795)
Summary
Path traversal in Microsoft.OpenApi.Kiota (CVE-2026-105795). Risk of unauthorized operations or information disclosure. Exploitable via Microsoft.OpenApi.Kiota. Mitigation: upgrade to 1.35.0 or later.
Original description
The description as published by the source.
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.co…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105795 has been found in Microsoft.OpenApi.Kiota.
Attackers can target a specific entry point like Microsoft.OpenApi.Kiota over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade Microsoft.OpenApi.Kiota to 1.35.0 or later.
If unsure, ask your IT team or search "Microsoft.OpenApi.Kiota CVE-2026-105795" on the vendor's site.
CVE-2026-105795 (Microsoft.OpenApi.Kiota) — CWE-22 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Microsoft.OpenApi.Kiota / Microsoft.OpenApi.Kiota.Builder / oauth_card_path / static_template.file
Patched: 1.35.0 — apply immediately
Workaround: Generate plugins only from trusted, integrity-protected OpenAPI descriptions.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in Microsoft.OpenApi.Kiota. Attackers reach the vulnerable code path via Microsoft.OpenApi.Kiota without authentication.
Check the vendor advisory for the affected versions of Microsoft.OpenApi.Kiota. Attack surface: Microsoft.OpenApi.Kiota / Microsoft.OpenApi.Kiota.Builder / oauth_card_path / static_template.file.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 1.35.0.
Workaround: Generate plugins only from trusted, integrity-protected OpenAPI descriptions.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Microsoft.OpenApi.Kiota' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Microsoft.OpenApi.Kiota' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Microsoft.OpenApi.Kiotaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Generate plugins only from trusted, integrity-protected OpenAPI descriptions.パッチが適用されるまでの応急処置として、Generate plugins only from trusted, integrity-protected OpenAPI descriptions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade Microsoft.OpenApi.Kiota to 1.35.0ステージング環境で 1.35.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com