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

AILast updated: 02/19/2026, 16:42:09 UTC

Technical Analysis

CVE-2026-26030 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code), affecting Microsoft’s Semantic Kernel Python SDK, specifically versions prior to 1.39.4. The vulnerability resides in the InMemoryVectorStore filter functionality, which improperly controls code generation, enabling remote code execution (RCE). An attacker with low privileges (PR:L) can exploit this flaw remotely (AV:N) without requiring user interaction (UI:N), leading to complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H). The vulnerability’s scope is changed (S:C), meaning it can affect resources beyond the initially vulnerable component. The root cause is improper sanitization or validation of inputs that are used in dynamic code generation or execution within the InMemoryVectorStore filter, allowing malicious payloads to be injected and executed. Microsoft addressed this issue in version 1.39.4 of the Semantic Kernel SDK. Until upgrading, users should avoid using the vulnerable InMemoryVectorStore filter in production environments. No public exploits have been reported yet, but the critical severity and ease of exploitation make it a significant threat, especially for organizations leveraging Semantic Kernel for AI-driven applications or semantic data processing.

Potential Impact

The impact of CVE-2026-26030 is severe, as it allows remote attackers to execute arbitrary code on affected systems, potentially leading to full system compromise. Confidential data handled by Semantic Kernel applications can be exposed or altered, undermining data integrity. Availability can be disrupted by malicious payloads causing denial of service or system crashes. Organizations relying on Semantic Kernel for AI or semantic processing may face operational disruptions, data breaches, or lateral movement within their networks. Given the vulnerability requires only low privileges and no user interaction, attackers can exploit it remotely with relative ease, increasing the risk of widespread attacks. The critical nature of this vulnerability demands immediate attention to prevent exploitation, especially in cloud environments, AI platforms, and services integrating Semantic Kernel components.

Mitigation Recommendations

The primary mitigation is to upgrade Microsoft Semantic Kernel SDK to version 1.39.4 or later, where the vulnerability is fixed. Until upgrading is feasible, organizations should avoid using the InMemoryVectorStore filter functionality in production environments. Implement strict network segmentation and access controls to limit exposure of systems running vulnerable versions. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious inputs targeting code injection vectors. Conduct thorough code reviews and input validation audits on any custom extensions or integrations using Semantic Kernel. Monitor logs and network traffic for unusual activity indicative of exploitation attempts. Establish incident response plans specific to AI/semantic processing components to rapidly contain potential breaches. Finally, maintain up-to-date backups and test recovery procedures to mitigate impact from potential exploitation.

Need more detailed analysis?Upgrade to Pro Console

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/19/2026, 4:42:09 PM

Last updated: 2/20/2026, 12:31:26 PM

Views: 88

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats