CVE-2026-26030
RCE in Semantic Kernel Python SDK InMemoryVectorStore (pre-1.39.4).
Is CVE-2026-26030 being exploited?
Not confirmed. CVE-2026-26030 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 3.7% probability of exploitation in the next 30 days.
How severe is CVE-2026-26030?
CVE-2026-26030 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-26030?
Yes. A fix has been recorded for CVE-2026-26030. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26030 affect?
CVE-2026-26030 affects Microsoft Semantic Kernel Python SDK, InMemoryVectorStore. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26030?
Upgrade to 1.39.4+; avoid InMemoryVectorStore in prod.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via InMemoryVectorStore filter; attacker could run arbitrary code with SDK privileges.
Immediate action required
- affected< 1.39.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.