Kiota
Monthly
Code injection in Microsoft Kiota 0.5.0 through pre-1.35.0 allows attacker-controlled text embedded in an OpenAPI description to break out of the generated Java or PHP documentation comment and execute in the consuming application or build environment once that generated source is compiled and loaded (Java) or loaded (PHP). The flaw is reachable unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but requires user interaction: a developer or CI pipeline must generate client code from an untrusted or tampered spec and then build or load the output, making this a build-time/supply-chain path rather than an attack on already-deployed runtime services. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV; CVSS 3.1 base score is 8.8, and the issue is fixed in 1.35.0.
Build-time SSRF, remote file inclusion, and local file inclusion in Microsoft Kiota before 1.32.5 lets an attacker-controlled OpenAPI description force the `kiota generate` command to fetch arbitrary remote http(s) URLs and read local absolute or out-of-tree file paths while resolving $ref values. Because Kiota inlined those external schemas into generated clients, an attacker could exfiltrate internal endpoints or leak local file contents (e.g. REMOTE_KIOTA_PROP-style properties) into produced code. No public exploit has been identified at time of analysis; the risk is developer/CI-toolchain oriented and requires a developer to run generation against a malicious or influenced description (CVSS 7.1).
Path traversal and code injection in Microsoft Kiota before 1.32.5 lets an attacker-controlled OpenAPI description write generated source files outside the intended output directory and inject arbitrary text into class/namespace declarations. When a developer runs `kiota generate` without the -c/--class-name flag, Kiota consumes the clientClassName and clientNamespaceName values from the OpenAPI `x-ms-kiota-info` extension without identifier or path sanitization, using them both as code identifiers and as filesystem path components. There is no public exploit identified at time of analysis and no CISA KEV listing, though the fix (SanitizeClientClassName/SanitizeClientNamespaceName) is visible in the merged patch.
Path traversal in Microsoft Kiota before 1.32.5 lets an attacker-controlled OpenAPI description inject unvalidated `static_template.file` values (via the x-ai-adaptive-card and x-ai-capabilities extensions) into generated Microsoft 365 Copilot and Teams plugin manifests, so a developer who runs `kiota plugin add` or `kiota plugin generate -t APIPlugin` against a malicious spec produces a manifest that resolves files outside its package when deployed. Rated CVSS 4.0 9.3 (Critical) with high confidentiality/integrity/availability impact and no privileges required. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the upstream fix is confirmed in release v1.32.5.
Command injection in Microsoft Kiota before 1.32.5 lets a malicious or compromised OpenAPI description dictate the install command that Kiota presents to developers. When a developer runs `kiota info` (or the VS Code extension's `kiota info --json` dependency-install flow) against an attacker-controlled spec, Kiota reads the `x-ms-kiota-info.languagesInformation.<language>.dependencyInstallCommand` field plus attacker-chosen dependency name/version values and surfaces them as its trusted recommended install command, achieving arbitrary command execution when that command is run. No public exploit has been identified at time of analysis and it is not in CISA KEV, but the fix explicitly removes the untrusted extension field.
Arbitrary file write via path traversal in Microsoft Kiota (OpenAPI HTTP client/plugin code generator) before 1.32.5 allows a malicious repository or pull request to place files outside the workspace root on a developer or CI host. The tool trusts the checked-in .kiota/workspace.json and honors attacker-controlled per-client and per-plugin outputPath values during 'kiota client generate' and 'kiota plugin generate' without validating them. No public exploit identified at time of analysis and the flaw is not in CISA KEV, but exploitation is realistic in CI/pull-request workflows since it only requires a developer to run generation against poisoned config.
PHP code generation in Microsoft Kiota prior to 1.32.4 permits injection of arbitrary PHP code when the generator processes attacker-controlled OpenAPI specification fields, because the shared `SanitizeDoubleQuote()` helper in `Writers/StringExtensions.cs` fails to escape the `$` character before embedding schema-derived strings into PHP double-quoted literals. Developers or CI/CD pipelines that generate PHP API clients from untrusted or third-party specifications will produce PHP files containing live interpolation expressions (`${...}`, `$var`, `{$obj->prop}`) that execute attacker-chosen code at PHP runtime in production environments. No public exploit has been identified and SSVC rates exploitation as currently none, but technical impact is rated total; the realistic risk is tightly gated on whether teams consume external or attacker-influenced specs without generated-code review.
Code injection in Microsoft Kiota's Python client generator (versions prior to 1.32.0) allows an attacker who controls an OpenAPI description to embed arbitrary Python that executes when a developer generates and imports the resulting client. The flaw stems from unsanitized x-ms-enum.values[].description strings being emitted as inline comments; embedded newlines break out of the comment and run at module scope. No public exploit identified at time of analysis, and the issue is not in CISA KEV. The assigned CVSS 3.1 base score is 7.5, though its impact metrics (C:N/I:N/A:H) understate what is functionally full code execution.
Code injection in Microsoft Kiota Ruby code generator allows remote code execution through crafted OpenAPI specifications. Kiota versions prior to 1.32.0 fail to escape '#' characters in schema-derived strings embedded in Ruby double-quoted literals, enabling Ruby interpolation sequences such as '#{code}' to execute arbitrary commands when the generated client code runs. While no active exploitation is confirmed, the attack is automatable, EPSS indicates moderate probability (1.47%), and the vendor has released a fix.
Code-generation injection in Microsoft Kiota's C# XML documentation-comment writer allows an attacker who controls or compromises an OpenAPI specification to inject arbitrary C# statements into generated client source files. Affected packages Microsoft.OpenApi.Kiota and Microsoft.OpenApi.Kiota.Builder in versions prior to 1.29.1 and in the 1.30.0-1.32.2 range fail to strip C# line-terminator characters from description and externalDocs fields before emitting them as single-line /// doc comments, enabling payload breakout into compilable namespace-level code. No public exploit confirmed in the wild at time of analysis, though SSVC reports a POC exists and rates technical impact as total; exploitation culminates when a developer or CI pipeline builds the tainted generated output.
Code injection in Microsoft Kiota versions prior to 1.31.1 allows attackers who control or tamper with OpenAPI descriptions to inject malicious code into generated HTTP client libraries. Exploitation requires developers to generate clients from untrusted or compromised OpenAPI specifications, then compile and execute the poisoned code. The attack chain culminates in arbitrary code execution within the context of applications using the tainted generated clients. CVSS 7.3 with local attack vector and user interaction required suggests lower immediate urgency, though EPSS data is unavailable. No public exploit code or active exploitation confirmed at time of analysis.
Microsoft Kiota, the OpenAPI-based HTTP client code generator, fails to validate the x-ai-capabilities.response_semantics.oauth_card_path value before copying it into a generated API plugin manifest, allowing path-traversal or absolute-URI references to survive into the manifest in versions 1.25.1 through 1.34.x. An attacker who controls or compromises the OpenAPI description can inject a malicious oauth_card_path (for example '../../../../etc/passwd', 'C:\\Windows\\...', a UNC path, or 'file:///etc/passwd') so that a downstream host resolving the plugin manifest crosses the intended plugin-package boundary or loads an unintended authentication card. The attacker vector is network-based and unauthenticated (PR:N), but exploitation requires a developer to actively run Kiota generation against the malicious description and a separate downstream consumer to resolve the reference; Kiota performs no file read or code execution during generation itself, so impact is limited to low integrity (I:L) and there is no public exploit identified at time of analysis. The issue is fixed in version 1.35.0.
Code injection in Microsoft Kiota 0.5.0 through pre-1.35.0 allows attacker-controlled text embedded in an OpenAPI description to break out of the generated Java or PHP documentation comment and execute in the consuming application or build environment once that generated source is compiled and loaded (Java) or loaded (PHP). The flaw is reachable unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but requires user interaction: a developer or CI pipeline must generate client code from an untrusted or tampered spec and then build or load the output, making this a build-time/supply-chain path rather than an attack on already-deployed runtime services. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV; CVSS 3.1 base score is 8.8, and the issue is fixed in 1.35.0.
Build-time SSRF, remote file inclusion, and local file inclusion in Microsoft Kiota before 1.32.5 lets an attacker-controlled OpenAPI description force the `kiota generate` command to fetch arbitrary remote http(s) URLs and read local absolute or out-of-tree file paths while resolving $ref values. Because Kiota inlined those external schemas into generated clients, an attacker could exfiltrate internal endpoints or leak local file contents (e.g. REMOTE_KIOTA_PROP-style properties) into produced code. No public exploit has been identified at time of analysis; the risk is developer/CI-toolchain oriented and requires a developer to run generation against a malicious or influenced description (CVSS 7.1).
Path traversal and code injection in Microsoft Kiota before 1.32.5 lets an attacker-controlled OpenAPI description write generated source files outside the intended output directory and inject arbitrary text into class/namespace declarations. When a developer runs `kiota generate` without the -c/--class-name flag, Kiota consumes the clientClassName and clientNamespaceName values from the OpenAPI `x-ms-kiota-info` extension without identifier or path sanitization, using them both as code identifiers and as filesystem path components. There is no public exploit identified at time of analysis and no CISA KEV listing, though the fix (SanitizeClientClassName/SanitizeClientNamespaceName) is visible in the merged patch.
Path traversal in Microsoft Kiota before 1.32.5 lets an attacker-controlled OpenAPI description inject unvalidated `static_template.file` values (via the x-ai-adaptive-card and x-ai-capabilities extensions) into generated Microsoft 365 Copilot and Teams plugin manifests, so a developer who runs `kiota plugin add` or `kiota plugin generate -t APIPlugin` against a malicious spec produces a manifest that resolves files outside its package when deployed. Rated CVSS 4.0 9.3 (Critical) with high confidentiality/integrity/availability impact and no privileges required. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the upstream fix is confirmed in release v1.32.5.
Command injection in Microsoft Kiota before 1.32.5 lets a malicious or compromised OpenAPI description dictate the install command that Kiota presents to developers. When a developer runs `kiota info` (or the VS Code extension's `kiota info --json` dependency-install flow) against an attacker-controlled spec, Kiota reads the `x-ms-kiota-info.languagesInformation.<language>.dependencyInstallCommand` field plus attacker-chosen dependency name/version values and surfaces them as its trusted recommended install command, achieving arbitrary command execution when that command is run. No public exploit has been identified at time of analysis and it is not in CISA KEV, but the fix explicitly removes the untrusted extension field.
Arbitrary file write via path traversal in Microsoft Kiota (OpenAPI HTTP client/plugin code generator) before 1.32.5 allows a malicious repository or pull request to place files outside the workspace root on a developer or CI host. The tool trusts the checked-in .kiota/workspace.json and honors attacker-controlled per-client and per-plugin outputPath values during 'kiota client generate' and 'kiota plugin generate' without validating them. No public exploit identified at time of analysis and the flaw is not in CISA KEV, but exploitation is realistic in CI/pull-request workflows since it only requires a developer to run generation against poisoned config.
PHP code generation in Microsoft Kiota prior to 1.32.4 permits injection of arbitrary PHP code when the generator processes attacker-controlled OpenAPI specification fields, because the shared `SanitizeDoubleQuote()` helper in `Writers/StringExtensions.cs` fails to escape the `$` character before embedding schema-derived strings into PHP double-quoted literals. Developers or CI/CD pipelines that generate PHP API clients from untrusted or third-party specifications will produce PHP files containing live interpolation expressions (`${...}`, `$var`, `{$obj->prop}`) that execute attacker-chosen code at PHP runtime in production environments. No public exploit has been identified and SSVC rates exploitation as currently none, but technical impact is rated total; the realistic risk is tightly gated on whether teams consume external or attacker-influenced specs without generated-code review.
Code injection in Microsoft Kiota's Python client generator (versions prior to 1.32.0) allows an attacker who controls an OpenAPI description to embed arbitrary Python that executes when a developer generates and imports the resulting client. The flaw stems from unsanitized x-ms-enum.values[].description strings being emitted as inline comments; embedded newlines break out of the comment and run at module scope. No public exploit identified at time of analysis, and the issue is not in CISA KEV. The assigned CVSS 3.1 base score is 7.5, though its impact metrics (C:N/I:N/A:H) understate what is functionally full code execution.
Code injection in Microsoft Kiota Ruby code generator allows remote code execution through crafted OpenAPI specifications. Kiota versions prior to 1.32.0 fail to escape '#' characters in schema-derived strings embedded in Ruby double-quoted literals, enabling Ruby interpolation sequences such as '#{code}' to execute arbitrary commands when the generated client code runs. While no active exploitation is confirmed, the attack is automatable, EPSS indicates moderate probability (1.47%), and the vendor has released a fix.
Code-generation injection in Microsoft Kiota's C# XML documentation-comment writer allows an attacker who controls or compromises an OpenAPI specification to inject arbitrary C# statements into generated client source files. Affected packages Microsoft.OpenApi.Kiota and Microsoft.OpenApi.Kiota.Builder in versions prior to 1.29.1 and in the 1.30.0-1.32.2 range fail to strip C# line-terminator characters from description and externalDocs fields before emitting them as single-line /// doc comments, enabling payload breakout into compilable namespace-level code. No public exploit confirmed in the wild at time of analysis, though SSVC reports a POC exists and rates technical impact as total; exploitation culminates when a developer or CI pipeline builds the tainted generated output.
Code injection in Microsoft Kiota versions prior to 1.31.1 allows attackers who control or tamper with OpenAPI descriptions to inject malicious code into generated HTTP client libraries. Exploitation requires developers to generate clients from untrusted or compromised OpenAPI specifications, then compile and execute the poisoned code. The attack chain culminates in arbitrary code execution within the context of applications using the tainted generated clients. CVSS 7.3 with local attack vector and user interaction required suggests lower immediate urgency, though EPSS data is unavailable. No public exploit code or active exploitation confirmed at time of analysis.
Microsoft Kiota, the OpenAPI-based HTTP client code generator, fails to validate the x-ai-capabilities.response_semantics.oauth_card_path value before copying it into a generated API plugin manifest, allowing path-traversal or absolute-URI references to survive into the manifest in versions 1.25.1 through 1.34.x. An attacker who controls or compromises the OpenAPI description can inject a malicious oauth_card_path (for example '../../../../etc/passwd', 'C:\\Windows\\...', a UNC path, or 'file:///etc/passwd') so that a downstream host resolving the plugin manifest crosses the intended plugin-package boundary or loads an unintended authentication card. The attacker vector is network-based and unauthenticated (PR:N), but exploitation requires a developer to actively run Kiota generation against the malicious description and a separate downstream consumer to resolve the reference; Kiota performs no file read or code execution during generation itself, so impact is limited to low integrity (I:L) and there is no public exploit identified at time of analysis. The issue is fixed in version 1.35.0.