Semantic Kernel has Arbitrary File Write via AI Agent Function Calling in .NET SDK
CVE-2026-25592 · GHSA-2ww3-72rp-wpp4 · published 2026-02-06 · updated 2026-02-20
- Severity
- Critical
- CVSS score
- 9.9
- Chance of exploitation (EPSS)
- 2.5%
- Fixed in
- 1.71.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
What kind of vulnerability is it? Who is impacted? An Arbitrary File Write vulnerability has been identified in Microsoft's Semantic Kernel .NET SDK, specifically within the SessionsPythonPlugin. Developers who have built applications which include Microsoft's Semantic Kernel .NET SDK and are using the SessionsPythonPlugin
Upgrade Microsoft.SemanticKernel.Core to 1.71.0 or later, and semantic-kernel to 1.39.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Has the problem been patched? What versions should users upgrade to? The problem has been fixed in Microsoft.SemanticKernel.Plugins.Core version 1.71.0. Users should upgrade to version 1.71.0 or higher.
Is there a way for users to fix or remediate the vulnerability without upgrading? Users can create a Function Invocation Filter which checks the arguments being passed to any calls to DownloadFileAsync or UploadFileAsync and ensures the provided localFilePath is allow listed.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| Microsoft.SemanticKernel.Core | NuGet | < 1.71.0 | 1.71.0 |
| semantic-kernel | PyPI | < 1.39.3 | 1.39.3 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.