Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-26030: CWE-94: Improper Control of Generation of Code ('Code Injection') in microsoft semantic-kernel

0
Critical
VulnerabilityCVE-2026-26030cvecve-2026-26030cwe-94
Published: Thu Feb 19 2026 (02/19/2026, 16:00:55 UTC)
Source: CVE Database V5
Vendor/Project: microsoft
Product: semantic-kernel

Description

Semantic Kernel, Microsoft's semantic kernel Python SDK, has a remote code execution vulnerability in versions prior to 1.39.4, specifically within the `InMemoryVectorStore` filter functionality. The problem has been fixed in version `python-1.39.4`. Users should upgrade this version or higher. As a workaround, avoid using `InMemoryVectorStore` for production scenarios.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 08:44:44 UTC

Technical Analysis

CVE-2026-26030 is a critical vulnerability identified in Microsoft’s Semantic Kernel Python SDK, specifically affecting versions prior to 1.39.4. The vulnerability arises from improper control of code generation (CWE-94) within the InMemoryVectorStore filter functionality. This flaw allows an attacker with limited privileges (PR:L) to perform remote code execution (RCE) without requiring user interaction (UI:N). The vulnerability is exploitable over the network (AV:N) with low attack complexity (AC:L), and it affects the confidentiality, integrity, and availability of affected systems severely (C:H/I:H/A:H). The scope of the vulnerability is changed (S:C), meaning the exploit can affect resources beyond the initially vulnerable component. The root cause is the unsafe handling of dynamic code generation or evaluation within the SDK’s filtering mechanism, which can be manipulated to inject and execute arbitrary code remotely. Microsoft addressed this issue in version 1.39.4 by correcting the code generation control mechanisms. Until upgrading, users are advised to avoid using the InMemoryVectorStore filter in production environments to mitigate risk. Although no active exploits have been reported, the vulnerability’s characteristics make it highly exploitable and dangerous, especially in environments relying on Semantic Kernel for AI and semantic processing workloads.

Potential Impact

The impact of CVE-2026-26030 is severe for organizations using Microsoft’s Semantic Kernel Python SDK, particularly those leveraging the InMemoryVectorStore filter functionality. Successful exploitation allows attackers to execute arbitrary code remotely, potentially leading to full system compromise, data theft, unauthorized access, and disruption of services. The vulnerability affects confidentiality by exposing sensitive data, integrity by allowing unauthorized code execution and modification, and availability by potentially causing denial-of-service conditions. Given the SDK’s role in AI and semantic processing applications, exploitation could undermine critical business functions, automated workflows, and data analytics pipelines. Organizations using this SDK in cloud environments, AI platforms, or integrated enterprise applications face heightened risk. The vulnerability’s ease of exploitation and lack of required user interaction increase the likelihood of rapid compromise once exploited. Without timely patching or mitigation, attackers could leverage this flaw to establish persistent footholds, move laterally, or exfiltrate sensitive information.

Mitigation Recommendations

To mitigate CVE-2026-26030, organizations should immediately upgrade Microsoft Semantic Kernel Python SDK to version 1.39.4 or later, where the vulnerability is patched. If upgrading is not immediately feasible, avoid using the InMemoryVectorStore filter functionality in production environments as a temporary workaround. Conduct thorough code reviews and audits of any custom code interacting with the SDK to ensure no unsafe dynamic code generation or evaluation occurs. Implement network segmentation and strict access controls to limit exposure of systems running vulnerable SDK versions. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to monitor for suspicious code execution behaviors. Regularly update and patch all dependencies and monitor vendor advisories for any further updates or exploit reports. Finally, integrate this vulnerability into incident response plans to enable rapid detection and remediation if exploitation attempts are observed.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-09T21:36:29.555Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69973b6be884a8a4cb409743

Added to database: 2/19/2026, 4:33:47 PM

Last enriched: 2/27/2026, 8:44:44 AM

Last updated: 4/6/2026, 5:48:34 PM

Views: 381

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses