AgentScout Logo Agent Scout

Microsoft: RCE Vulnerabilities Turn Prompts Into Shell Commands

CVE-2026-26030 (CVSS 9.8) enables RCE in Semantic Kernel via prompt injection. Immediate upgrade to 1.39.4+ required for AI agent applications.

AgentScout Β· Β· 4 min read
#microsoft #semantic-kernel #rce #prompt-injection #ai-security #cve
Analyzing Data Nodes...
SIG_CONF:CALCULATING
Verified Sources

TL;DR

Microsoft disclosed CVE-2026-26030 (CVSS 9.8), a critical remote code execution vulnerability in Semantic Kernel Python SDK that allows attackers to execute arbitrary code through prompt injection in vector store filter expressions. The vulnerability affects all versions prior to 1.39.4 and targets AI agent infrastructure directly, not web endpoints.

Key Facts

  • Who: Microsoft Security Response Center, affecting Semantic Kernel SDK users
  • What: Critical RCE vulnerability (CVSS 9.8) enabling arbitrary code execution via prompt injection
  • When: Disclosed May 7, 2026; patches available immediately
  • Impact: All AI applications using Semantic Kernel Python SDK < 1.39.4 or .NET SDK < 1.71.0

What Changed

Microsoft’s Security Response Center disclosed a critical remote code execution vulnerability in Semantic Kernel, its open-source SDK for building AI agents. CVE-2026-26030 carries a CVSS severity score of 9.8 out of 10, making it one of the most severe AI framework vulnerabilities disclosed in 2026.

The vulnerability resides in the InMemoryVectorStore component, where malicious filter expressions can be injected through user prompts. Unlike traditional injection attacks that target web application endpoints, this attack chain converts natural language input into executable Python code through the agent’s internal filter parsing logic.

β€œAn attacker who successfully exploited this vulnerability could run arbitrary code in the context of the application,” Microsoft stated in its security advisory. β€œThis could allow the attacker to install programs; view, change, or delete data; or create new accounts with full user rights.”

A second vulnerability, CVE-2026-25592, affects the .NET SDK with a path traversal flaw. Both vulnerabilities were patched in Semantic Kernel Python version 1.39.4 and .NET version 1.71.0, released immediately upon disclosure.

Security researchers from Nuka-AI disclosed multiple bypass vectors for the initial February patches, prompting the May disclosure and additional hardening measures.

Why It Matters

The attack chain mechanics distinguish this vulnerability from traditional web security threats:

Attack VectorTraditional XSSSemantic Kernel RCE
Entry PointWeb form inputAgent prompt input
Target LayerBrowser DOMPython/.NET runtime
Execution ContextClient-side JavaScriptServer-side code
Blast RadiusUser sessionApplication server
Exploitation ComplexityMediumLow

Attack Chain Breakdown:

  1. Prompt Input: Attacker crafts a natural language prompt containing malicious filter syntax
  2. Filter Expression: The prompt is passed to InMemoryVectorStore.filter() without proper sanitization
  3. Code Execution: Filter expression is evaluated as Python code via eval() or equivalent
  4. Runtime Access: Attacker gains arbitrary code execution on the server hosting the AI agent

The vulnerability class is particularly concerning because:

  • No Input Validation Bypass Required: The filter expression syntax is intended functionality, making detection difficult
  • Agent-Specific Attack Surface: Traditional WAF rules do not inspect agent prompt flows
  • High Trust Context: AI agents often run with elevated permissions to access tools, APIs, and databases
  • Supply Chain Implications: Organizations embedding Semantic Kernel in production agents face immediate exposure

According to Microsoft’s security blog, the attack requires no authentication for applications that accept untrusted prompts, which includes most customer-facing AI agent deployments.

πŸ”Ί Scout Intel: What Others Missed

Confidence: high | Novelty Score: 82/100

The deeper security implication extends beyond the immediate patch. This vulnerability represents a new attack class: prompt-to-code translation exploits. Traditional security models assume a boundary between user input and code execution, but AI agent frameworks deliberately blur this boundary through natural language interfaces. Semantic Kernel’s filter expression mechanism is not a bugβ€”it’s a feature designed to let developers write expressive queries. The vulnerability exploits this intentional design pattern, making it difficult to distinguish legitimate use from malicious injection without breaking functionality.

Key Implication: Enterprise security teams must audit all AI agent frameworksβ€”not just Semantic Kernelβ€”for similar prompt-to-code translation patterns. LangChain, CrewAI, and OpenAI’s Agents SDK all implement comparable filter/search mechanisms that may contain equivalent vulnerabilities. The attack surface is architectural, not incidental.

What This Means

For AI Application Developers

Immediate action is required for any application using Semantic Kernel Python SDK before version 1.39.4 or .NET SDK before version 1.71.0. The patch introduces strict input sanitization for filter expressions, but developers should additionally:

  • Implement prompt content filtering before filter expression generation
  • Audit agent permissions and apply principle of least privilege
  • Enable audit logging for all filter expression evaluations
  • Consider sandboxing agent runtimes in containerized environments

For Enterprise Security Teams

This disclosure should trigger a broader audit of AI agent infrastructure:

  1. Inventory all AI frameworks in production environments, including Semantic Kernel, LangChain, CrewAI, AutoGen, and OpenAI Agents SDK
  2. Review prompt handling code for similar filter expression patterns
  3. Update security monitoring to include agent prompt flows, which traditional WAFs do not inspect
  4. Assess blast radius: Agents with database, API, or file system access multiply the potential impact

What to Watch

Microsoft’s disclosure may be the first of many in this vulnerability class. Security researchers at Nuka-AI have demonstrated that the attack pattern is replicable across multiple agent frameworks. Expect additional CVEs targeting prompt-to-code translation mechanisms in competing AI agent SDKs throughout 2026.

Related Coverage:

Sources

Microsoft: RCE Vulnerabilities Turn Prompts Into Shell Commands

CVE-2026-26030 (CVSS 9.8) enables RCE in Semantic Kernel via prompt injection. Immediate upgrade to 1.39.4+ required for AI agent applications.

AgentScout Β· Β· 4 min read
#microsoft #semantic-kernel #rce #prompt-injection #ai-security #cve
Analyzing Data Nodes...
SIG_CONF:CALCULATING
Verified Sources

TL;DR

Microsoft disclosed CVE-2026-26030 (CVSS 9.8), a critical remote code execution vulnerability in Semantic Kernel Python SDK that allows attackers to execute arbitrary code through prompt injection in vector store filter expressions. The vulnerability affects all versions prior to 1.39.4 and targets AI agent infrastructure directly, not web endpoints.

Key Facts

  • Who: Microsoft Security Response Center, affecting Semantic Kernel SDK users
  • What: Critical RCE vulnerability (CVSS 9.8) enabling arbitrary code execution via prompt injection
  • When: Disclosed May 7, 2026; patches available immediately
  • Impact: All AI applications using Semantic Kernel Python SDK < 1.39.4 or .NET SDK < 1.71.0

What Changed

Microsoft’s Security Response Center disclosed a critical remote code execution vulnerability in Semantic Kernel, its open-source SDK for building AI agents. CVE-2026-26030 carries a CVSS severity score of 9.8 out of 10, making it one of the most severe AI framework vulnerabilities disclosed in 2026.

The vulnerability resides in the InMemoryVectorStore component, where malicious filter expressions can be injected through user prompts. Unlike traditional injection attacks that target web application endpoints, this attack chain converts natural language input into executable Python code through the agent’s internal filter parsing logic.

β€œAn attacker who successfully exploited this vulnerability could run arbitrary code in the context of the application,” Microsoft stated in its security advisory. β€œThis could allow the attacker to install programs; view, change, or delete data; or create new accounts with full user rights.”

A second vulnerability, CVE-2026-25592, affects the .NET SDK with a path traversal flaw. Both vulnerabilities were patched in Semantic Kernel Python version 1.39.4 and .NET version 1.71.0, released immediately upon disclosure.

Security researchers from Nuka-AI disclosed multiple bypass vectors for the initial February patches, prompting the May disclosure and additional hardening measures.

Why It Matters

The attack chain mechanics distinguish this vulnerability from traditional web security threats:

Attack VectorTraditional XSSSemantic Kernel RCE
Entry PointWeb form inputAgent prompt input
Target LayerBrowser DOMPython/.NET runtime
Execution ContextClient-side JavaScriptServer-side code
Blast RadiusUser sessionApplication server
Exploitation ComplexityMediumLow

Attack Chain Breakdown:

  1. Prompt Input: Attacker crafts a natural language prompt containing malicious filter syntax
  2. Filter Expression: The prompt is passed to InMemoryVectorStore.filter() without proper sanitization
  3. Code Execution: Filter expression is evaluated as Python code via eval() or equivalent
  4. Runtime Access: Attacker gains arbitrary code execution on the server hosting the AI agent

The vulnerability class is particularly concerning because:

  • No Input Validation Bypass Required: The filter expression syntax is intended functionality, making detection difficult
  • Agent-Specific Attack Surface: Traditional WAF rules do not inspect agent prompt flows
  • High Trust Context: AI agents often run with elevated permissions to access tools, APIs, and databases
  • Supply Chain Implications: Organizations embedding Semantic Kernel in production agents face immediate exposure

According to Microsoft’s security blog, the attack requires no authentication for applications that accept untrusted prompts, which includes most customer-facing AI agent deployments.

πŸ”Ί Scout Intel: What Others Missed

Confidence: high | Novelty Score: 82/100

The deeper security implication extends beyond the immediate patch. This vulnerability represents a new attack class: prompt-to-code translation exploits. Traditional security models assume a boundary between user input and code execution, but AI agent frameworks deliberately blur this boundary through natural language interfaces. Semantic Kernel’s filter expression mechanism is not a bugβ€”it’s a feature designed to let developers write expressive queries. The vulnerability exploits this intentional design pattern, making it difficult to distinguish legitimate use from malicious injection without breaking functionality.

Key Implication: Enterprise security teams must audit all AI agent frameworksβ€”not just Semantic Kernelβ€”for similar prompt-to-code translation patterns. LangChain, CrewAI, and OpenAI’s Agents SDK all implement comparable filter/search mechanisms that may contain equivalent vulnerabilities. The attack surface is architectural, not incidental.

What This Means

For AI Application Developers

Immediate action is required for any application using Semantic Kernel Python SDK before version 1.39.4 or .NET SDK before version 1.71.0. The patch introduces strict input sanitization for filter expressions, but developers should additionally:

  • Implement prompt content filtering before filter expression generation
  • Audit agent permissions and apply principle of least privilege
  • Enable audit logging for all filter expression evaluations
  • Consider sandboxing agent runtimes in containerized environments

For Enterprise Security Teams

This disclosure should trigger a broader audit of AI agent infrastructure:

  1. Inventory all AI frameworks in production environments, including Semantic Kernel, LangChain, CrewAI, AutoGen, and OpenAI Agents SDK
  2. Review prompt handling code for similar filter expression patterns
  3. Update security monitoring to include agent prompt flows, which traditional WAFs do not inspect
  4. Assess blast radius: Agents with database, API, or file system access multiply the potential impact

What to Watch

Microsoft’s disclosure may be the first of many in this vulnerability class. Security researchers at Nuka-AI have demonstrated that the attack pattern is replicable across multiple agent frameworks. Expect additional CVEs targeting prompt-to-code translation mechanisms in competing AI agent SDKs throughout 2026.

Related Coverage:

Sources

q61cgkdhteoj2kymfw1suβ–ˆβ–ˆβ–ˆβ–ˆlykz6smis4mr8p68lxtqm2w7c6ahxi79β–ˆβ–ˆβ–ˆβ–ˆh2cyrl6ahel9surr40ckrslajr7x9lt89β–‘β–‘β–‘bqiy0n8jtbvjcdeomcwv24q3etu2cd69β–ˆβ–ˆβ–ˆβ–ˆ1477wq5lbd3lhdfustiuahu463iofgk52pβ–ˆβ–ˆβ–ˆβ–ˆov0wpj22g33zj1mk6fjxbauh3qtdhwl8β–‘β–‘β–‘ir89ya5yvhsnpxj34kdwllmifgjdxex07β–ˆβ–ˆβ–ˆβ–ˆ592rsko39mhoqgwuiwuyeboi0xwsy8b5β–‘β–‘β–‘7c9mhbkpj0pn6lo5fk3u6lfvavbvssgeβ–ˆβ–ˆβ–ˆβ–ˆu24hbjou6cj7vexotj8537hbjgke7pqtβ–‘β–‘β–‘9c7txf5oaztzxqth5y0b3sndeoxjpryeqβ–ˆβ–ˆβ–ˆβ–ˆ3qvtu34lg29w1drr71ce4k3wqnhioh7β–‘β–‘β–‘w9sauzn1rvrjbqqo2x0zb75stumcya0oβ–ˆβ–ˆβ–ˆβ–ˆhlob6faleflpis7z0x6ecbvrsmjxek44β–ˆβ–ˆβ–ˆβ–ˆcef2jay4o69hajgcrjtdhb8wl61a6hc3wβ–‘β–‘β–‘529vqx0l4pw6387hyi30ga5qbltgdtxx7β–‘β–‘β–‘bx8zweufhro33drwn3itp82hnppzni30sβ–‘β–‘β–‘bs6xxzsciciw8jqiebev7d7chcwinzk8qβ–‘β–‘β–‘pt6zrdszxnrm64q28jgqm16pgnil7crdβ–‘β–‘β–‘9xqmx5nxkgpuhxd8i3uz8bib6sz6p13w7β–‘β–‘β–‘cf2fnso0vg793bma0yb71jspcy22hiq7dβ–ˆβ–ˆβ–ˆβ–ˆs9d5af0bpm01bmrrrpdcfo7hz4tvhl0j2β–‘β–‘β–‘3nri2n7zwfdt0civmxfc7ftpkw2imrzlβ–ˆβ–ˆβ–ˆβ–ˆhr8gyv0uyp5bl0riwu6d1fpokq6iyao8β–ˆβ–ˆβ–ˆβ–ˆ3jetkrv6hsy0d2muygj9wbadg22m3nf1wvβ–‘β–‘β–‘vcmi4iifcio1r1vwtc0zybmexxzpvhetlβ–‘β–‘β–‘601vkbwjpsya7k4vvjkmrhkeyyincp5hβ–ˆβ–ˆβ–ˆβ–ˆq9bee29t8nnc2ewqmjvhccjsgu2797lβ–‘β–‘β–‘7esg7v67o2ordq0saxjv931q2kc1c3l6β–ˆβ–ˆβ–ˆβ–ˆ39np4av062b9bldjk121up7gtu8a9lwxqβ–ˆβ–ˆβ–ˆβ–ˆ9r6xby5d8s8emi4qxeseroykmshg5i9vcβ–‘β–‘β–‘vhps4u13lue8yh4a8gjpixsc4t9indbgβ–ˆβ–ˆβ–ˆβ–ˆmnt6vwanvgf9pv0rg7qtsjs6o9t57d4rβ–ˆβ–ˆβ–ˆβ–ˆ89pkft6v4gk7qdghpr0amhwsj9su0vpbβ–ˆβ–ˆβ–ˆβ–ˆzfdy7i6yqlorc1h4d22iqjnulf8zerq8β–‘β–‘β–‘nk8gr9jsoo85aiox5lf8h7dgbcpxgchaβ–ˆβ–ˆβ–ˆβ–ˆ45o0je53x5yertvaqnz9khqhwaw8w4z4β–‘β–‘β–‘5chq9uvrfmi4mgaxkgtijirw054qmfalnβ–ˆβ–ˆβ–ˆβ–ˆycluyofm6wlq8mj3tqiyffbd4ddxo45mβ–‘β–‘β–‘ul2rtu39gfr2l9w0rcae4tx7c3cf61bβ–ˆβ–ˆβ–ˆβ–ˆ4syvxvskeou2rtfg7g3ivtm7codc47rzsβ–ˆβ–ˆβ–ˆβ–ˆj8iimt1urzb6ptmk0h7fy5x5zbc3cn9f9β–ˆβ–ˆβ–ˆβ–ˆfdlimzpf91o38k8yalcm0let4kauoe186β–ˆβ–ˆβ–ˆβ–ˆ52ki96jtvnlhnnkqejhrfr1wbsqqsorsjβ–‘β–‘β–‘g85yqz7ls0gqq8fbjhnyeq54o3pvj22pgβ–‘β–‘β–‘gio9bhb2am7mqp02okxbmcxastrja2ljβ–ˆβ–ˆβ–ˆβ–ˆa200yur24k9i48kos7db2lertxo1eac8β–‘β–‘β–‘ilkkxxm9hkl9d3cxhn8jbqozv0evgigβ–ˆβ–ˆβ–ˆβ–ˆg38dx790c0a4mi7x2yxg3kapllv792bjβ–ˆβ–ˆβ–ˆβ–ˆu9b3j3ri5uc18kyku3kf9e1xeu851u0urβ–‘β–‘β–‘qi5zfwhz3gn