Introducing The Sweep: OX’s New Live Security Research Series
Register Now
Breaking: The 2026 Vulnpocalypse Hits PHP: Four Critical RCEs, but How Dangerous Are They?
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-105795

Kiota: Unsafe oauth_card_path references in Kiota-generated API plugin manifests

Overview

Published
6 Oct 2026
Modified
6 Oct 2026
Low CVE
2 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available

Description

Kiota is an OpenAPI based HTTP Client code generator. From 1.25.1 until 1.35.0, Kiota copies x-ai-capabilities.response_semantics.oauth_card_path from an attacker-controlled or compromised OpenAPI description into a generated API plugin manifest without validating that the value is a safe package-relative file reference. Parent-directory traversal, rooted paths, or absolute URIs can therefore reach a consuming host that resolves the reference, allowing the host to cross the intended plugin-package boundary or use an unintended authentication card. Kiota does not itself read a local file or execute code merely while generating the manifest, and impact requires downstream resolution of the unsafe reference. This issue is fixed in version 1.35.0.

Source: OX vulnerability database

Severity

3.1 · LOW

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Weakness: CWE-22

Affected packages · 2

Packages affected by CVE-2026-105795
EcosystemPackageVulnerableFixed in
NuGet Microsoft.OpenApi.Kiota >=1.25.1, <1.35.0 1.35.0
NuGet Microsoft.OpenApi.Kiota.Builder >=1.25.1, <1.35.0 1.35.0

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.