dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-59864

CRITICAL · 9.3 CVSS v4.0 Published 2026-07-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.5, `kiota plugin add` and `kiota plugin generate` (with `-t APIPlugin`) emitted attacker-controlled static_template.file values from x-ai-adaptive-card and x-ai-capabilities into generated Microsoft 365 Copilot and Teams plugin manifests without path validation, allowing ../, absolute, rooted, UNC, Windows drive, or URI paths in response_semantics.static_template.file to cause path traversal or out-of-package file inclusion when the generated plugin was deployed. This issue is fixed in version 1.29.1 and 1.32.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kiota code generator prior to 1.29.1 and 1.32.5 fails to validate file paths from x-ai-adaptive-card and x-ai-capabilities extensions when generating Microsoft 365 Copilot and Teams plugin manifests. Attackers can embed path traversal sequences (../), absolute paths, UNC paths, Windows drive letters, or URI paths into static_template.file values, causing the generated plugin to read or include files outside the intended package directory upon deployment.

MitigationUpgrade Kiota to version 1.29.1 or 1.32.5 to receive the path validation fix; alternatively, audit any existing generated plugin manifests and remove or sanitize response_semantics.static_template.file values containing traversal sequences or absolute paths before deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Kiota version
    Run `kiota --version` and compare the output to 1.32.5. Versions below 1.32.5 are vulnerable.
    Affected if Installed version is less than 1.32.5
  2. Identify generated plugin manifests
    Search the filesystem for plugin manifest files (.json) created via `kiota plugin add` or `kiota plugin generate -t APIPlugin` commands. Note their locations and creation timestamps.
    Affected if Any plugin manifest files exist that were generated with a Kiota version below 1.32.5
  3. Inspect static_template.file values in generated manifests
    Open each identified manifest JSON file and locate the `response_semantic.static_template.file` field within x-ai-adaptive-card or x-ai-capabilities extension objects. Examine the file value for path traversal sequences (../), absolute paths starting with / or \, Windows drive letters (C:, D:), UNC paths (\\), or URI schemes (http:, https:).
    Affected if The static_template.file field contains any path traversal sequences, absolute paths, UNC paths, drive letters, or URI paths rather than simple relative filenames

A user is affected if they used Kiota versions prior to 1.32.5 to generate plugin manifests containing x-ai-adaptive-card or x-ai-capabilities extensions with suspicious path values in response_semantic.static_template.file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Kiota to version 1.29.1 or 1.32.5 to receive the path validation fix; alternatively, audit any existing generated plugin manifests and remove or sanitize response_semantics.static_template.file values containing traversal sequences or absolute paths before deployment.

Recommended fix High confidence

1.32.5

  1. Upgrade Kiota to version 1.32.5 or later. If using a package manager (e.g., dotnet tool install --global dotnet-kiota), run: `dotnet tool update -g dotnet-kiota --version 1.32.5`
  2. If using the standalone installer or binary, download version 1.32.5 or later from the official Kiota releases page at github.com/microsoft/kiota
  3. Verify the upgrade was successful by running: `kiota --version` and confirming the version number is 1.32.5 or higher
  4. Regenerate any plugin manifests using `kiota plugin add` or `kiota plugin generate -t APIPlugin` to ensure the new version's path validation is applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59864 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data