← Back
CVE-2026-59864
Path Traversal in Microsoft.OpenApi.Kiota (CVE-2026-59864)
Summary
path traversal in Microsoft.OpenApi.Kiota (CVE-2026-59864). Risk of unauthorized operations or information disclosure. Exploitable via ``static_template.file``. Mitigation: upgrade to `1.29.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59864** has been found in Microsoft.OpenApi.Kiota.
Attackers can target a specific entry point like ``static_template.file`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade Microsoft.OpenApi.Kiota to **1.29.1** or later.
If unsure, ask your IT team or search "Microsoft.OpenApi.Kiota CVE-2026-59864" on the vendor's site.
CVE-2026-59864 (Microsoft.OpenApi.Kiota) — CWE-22 /
Attack surface: `static_template.file` / `response_semantics.static_template.file` / `static_template` / `title`
Patched: `1.29.1` — apply immediately
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in Microsoft.OpenApi.Kiota. Attackers reach the vulnerable code path via ``static_template.file`` without authentication.
📍 Affected scope
Microsoft.OpenApi.Kiota — . Attack surface: `static_template.file` / `response_semantics.static_template.file` / `static_template` / `title`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.29.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Microsoft.OpenApi.Kiota to 1.29.1ステージング環境で 1.29.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
Microsoft.OpenApi.Kiota
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.29.1"}]}]
nuget
Microsoft.OpenApi.Kiota.Builder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.29.1"}]}]