For your digest
semantic-kernel, Microsoft.SemanticKernel.Core: Semantic Kernel has Arbitrary File Write via AI Agent Function Calling in .NET SDK
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- semantic-kernel (PyPI): every version, before 1.39.3
- Microsoft.SemanticKernel.Core (NuGet): every version, before 1.71.0
- semantic-kernel (PyPI): every version, before 1.39.3
The fix
semantic-kernel (PyPI) fixed in 1.39.3
pippython -m pip install semantic-kernel==1.39.3uvuv add semantic-kernel==1.39.3poetrypoetry add semantic-kernel@1.39.3Check what is installedpython -m pip show semantic-kernelPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency semantic-kernel to 1.39.3 or the nearest later release, to fix CVE-2026-25592. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.Microsoft.SemanticKernel.Core (NuGet) fixed in 1.71.0
dotnetdotnet add package Microsoft.SemanticKernel.Core --version 1.71.0Check what is installeddotnet list packagePaste into Cursor, Lovable or Claude CodeUpgrade the NuGet dependency Microsoft.SemanticKernel.Core to 1.71.0 or the nearest later release, to fix CVE-2026-25592. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".