Semantic KernelApplication · Microsoft
CVE-2026-26030
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSemantic 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSemantic Kernel Python SDK versions before 1.39.4 contain a remote code execution vulnerability in the InMemoryVectorStore filter functionality. The vulnerability allows attackers to execute arbitrary code through malicious input processed by the filter mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Semantic KernelApplication
< 1.39.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Semantic Kernel Python SDK versionRun 'pip show semantic-kernel' or 'pip list | grep semantic-kernel' to see the installed version numberAffected if The installed version is earlier than 1.39.4
-
Verify InMemoryVectorStore usageSearch your codebase for imports and instantiations of 'InMemoryVectorStore' from semantic_kernelAffected if Your code uses the InMemoryVectorStore class from the Semantic Kernel Python SDK
-
Identify filter input in vector queriesLocate code that calls query or search methods on InMemoryVectorStore and passes data to the filter parameterAffected if Your vector store query methods accept external or user-controlled data as filter arguments
-
Check production exposureAudit production deployments to determine if InMemoryVectorStore is accessible to untrusted users or external systemsAffected if InMemoryVectorStore with filter functionality is exposed in production without input sanitization
You are affected if you use Semantic Kernel Python SDK version lower than 1.39.4 and your application passes untrusted input to the filter parameter of InMemoryVectorStore query methods.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.39.4
Upgrade to python-1.39.4 or higher. As a temporary workaround, avoid using InMemoryVectorStore for production scenarios until the upgrade is completed.
python-1.39.4
- Upgrade the Semantic Kernel Python SDK to version 1.39.4 or higher using pip: pip install --upgrade semantic-kernel>=1.39.4
- Verify the installation by checking the installed version: python -c 'import semantic_kernel; print(semantic_kernel.__version__)'
- Ensure any production environments are restarted to load the updated package
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Semantic Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26030 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data