← Back
CVE-2026-25592
Path Traversal in semantic-kernel (CVE-2026-25592)
Summary
path traversal in semantic-kernel (CVE-2026-25592). Successful exploitation can lead to full system takeover. Exploitable via ``SessionsPythonPlugin``. Mitigation: upgrade to `1.39.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25592** has been found in semantic-kernel.
Attackers can target a specific entry point like ``SessionsPythonPlugin`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade semantic-kernel to **1.39.3** or later.
If unsure, ask your IT team or search "semantic-kernel CVE-2026-25592" on the vendor's site.
CVE-2026-25592 (semantic-kernel) — CWE-22 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `SessionsPythonPlugin` / `UploadFileAsync` / `localFilePath`
Patched: `1.39.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in semantic-kernel. Attackers reach the vulnerable code path via ``SessionsPythonPlugin`` without authentication.
📍 Affected scope
semantic-kernel — . Attack surface: `SessionsPythonPlugin` / `UploadFileAsync` / `localFilePath`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.39.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'semantic-kernel' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'semantic-kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `semantic-kernel` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade semantic-kernel to 1.39.3ステージング環境で 1.39.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
semantic-kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.39.3"}]}]
NuGet
Microsoft.SemanticKernel.Core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.71.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-25592
- advisory https://github.com/advisories/GHSA-2ww3-72rp-wpp4
- package https://github.com/microsoft/semantic-kernel
- package https://pypi.org/project/semantic-kernel
- web https://github.com/microsoft/semantic-kernel/security/advisories/GHSA-2ww3-72rp-wpp4
- web https://github.com/microsoft/semantic-kernel/pull/13478/changes#diff-88d3cacba2bfa84eef8f2aa171b34f9940338cbb784a3ffc49f5fe3af1b8943d
- web https://github.com/microsoft/semantic-kernel/blob/main/dotnet/samples/Demos/CodeInterpreterPlugin/Program.cs#L61-L64