critical

CVE-2026-25592

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

Published 6 Feb 2026Modified 17 Jun 2026CWE 22

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

GHSA10.0CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by GHSA.

Description

Semantic Kernel is an SDK used to build, orchestrate, and deploy AI agents and multi-agent systems. Prior to 1.71.0, an Arbitrary File Write vulnerability has been identified in Microsoft's Semantic Kernel .NET SDK, specifically within the SessionsPythonPlugin. The problem has been fixed in Microsoft.SemanticKernel.Core version 1.71.0. As a mitigation, 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.

Affected packages and fixed versions

Source	Package	Fixed in
nuget::GitHub Security Advisory NuGet	Microsoft.SemanticKernel.Core, microsoft.semantickernel.core	1.71.0
pip::GitHub Security Advisory pip	semantic-kernel	1.39.3

Show all 3 entries from 2 sources

Source	Package	Fixed in
nuget::GitHub Security Advisory NuGet	Microsoft.SemanticKernel.Core	1.71.0
nuget::GitHub Security Advisory NuGet	microsoft.semantickernel.core	1.71.0
pip::GitHub Security Advisory pip	semantic-kernel	1.39.3

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs