Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

Semantic Kernel has Arbitrary File Write via AI Agent Function Calling in .NET SDK

CVE-2026-25592GHSA-2ww3-72rp-wpp4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.semantickernel.core 1.71.0; semantic-kernel 1.39.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-25592: 2.52% estimated exploitation activity in the next 30 days; percentile 84.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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 Patches 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. Workarounds 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. References Are there any links users can visit to find out more? - Sample showing safe use of the CodeInterpreterPlugin - PR to Add file upload security controls to…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-2ww3-72rp-wpp4

  2. Revision 2 · amended ·

    Amended from osv record GHSA-2ww3-72rp-wpp4

  3. Revision 1 · created ·

    Published from ghsa record GHSA-2ww3-72rp-wpp4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25592

Advisory: Semantic Kernel has Arbitrary File Write via AI Agent Function Calling in .NET SDK
IDs: CVE-2026-25592, GHSA-2ww3-72rp-wpp4
Record: https://patchnext.com/advisories/cve-2026-25592 (revision 3, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.semantickernel.core 1.71.0; semantic-kernel 1.39.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.semantickernel.core: affected < 1.71.0; fixed in 1.71.0
- PyPI semantic-kernel: affected < 1.39.3; fixed in 1.39.3

## Suggested inspection (read-only)
- NuGet microsoft.semantickernel.core: check the installed version with your package manager.
- `python -m pip show semantic-kernel`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.semantickernel.core, semantic-kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2ww3-72rp-wpp4 (GitHub-reviewed advisory GHSA-2ww3-72rp-wpp4 lists affected ranges: PyPI semantic-kernel >=0 <1.39.3)
- Verified: https://osv.dev/vulnerability/GHSA-2ww3-72rp-wpp4 (OSV record GHSA-2ww3-72rp-wpp4 lists affected ranges: PyPI semantic-kernel >=0 =0 <1.71.0 (fixed))
- Verified: https://github.com/advisories/GHSA-2ww3-72rp-wpp4 (GitHub-reviewed advisory GHSA-2ww3-72rp-wpp4 lists affected ranges: PyPI semantic-kernel >=0 =0 <1.71.0)

Commands are suggestions: review each one before running it.

Loading voting…