https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T22:51:52.284170+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-354342 EUVD-2026-354342 2026-10-07T22:51:52.340797+00:00 EUVD-2026-354342 https://cve.radiocsirt.org/vuln/fkie_cve-2026-73851 fkie_cve-2026-73851 2026-10-07T22:51:52.340842+00:00

Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.34.0, an attacker who controls or tampers with the OpenAPI description consumed by Kiota can supply a file reference that resolves outside the manifest package (e.g. ../../../../etc/passwd, an absolute path, or a file:// / http(s):// URI). When the generated manifest is deployed and consumed by an AI host, this can lead to inclusion or disclosure of files outside the intended package boundary. This vulnerability is fixed in 1.29.1 and 1.34.0.

 https://cve.radiocsirt.org/vuln/ghsa-p5rm-jg5c-8c77 GHSA-p5rm-jg5c-8c77 — Microsoft Kiota: Path traversal in generated plugin manifest static_template.file reference (percent-encoding bypass) 2026-10-07T22:51:52.340882+00:00

Affected: NuGet: Microsoft.OpenApi.Kiota

### Impact

Kiota generates AI plugin manifests from an OpenAPI description. When the description contains an `x-ai-capabilities` response semantics `static_template` (or the adaptive-card extension `x-ai-adaptive-card`), the `file` reference is written into the generated manifest's `response_semantics.static_template.file` and is later resolved by the AI host **relative to the plugin package**.

An attacker who controls or tampers with the OpenAPI description consumed by Kiota can supply a `file` reference that resolves **outside** the manifest package (e.g. `../../../../etc/passwd`, an absolute path, or a `file://` / `http(s)://` URI). When the generated manifest is deployed and consumed by an AI host, this can lead to inclusion or disclosure of files outside the intended package boundary (CWE-22 Path Traversal, CWE-829 Inclusion of Functionality from an Untrusted Control Sphere).

A mitigation shipped in v1.32.5 (`ExtensionResponseSemanticsStaticTemplate.IsSafeFileReference`) rejected literal traversal, rooted paths, drive-qualified paths, and absolute URIs. However, that check inspected the **raw** reference string, so **percent-encoded** payloads bypassed every check and were still emitted verbatim. Examples that were incorrectly accepted as safe:

| Input | Decodes to | |-------|-----------| | `%2e%2e/card.json` | `../card.json` | | `..%2f..%2f..%2f..%2f..%2f..%2fetc%2fpasswd` | `../../../../../../etc/passwd` | | `file%3A%2F%2F%2Fetc%2Fpasswd` | `file:///etc/passwd` |…