This critical-severity CVE scores 9.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 2.9%, top 14% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
Microsoft Semantic Kernel InMemoryVectorStore filter functionality vulnerable to remote code execution
InMemoryVectorStore filter functionality.InMemoryVectorStore for production scenarios.EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
February 19, 2026
February 19, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
GitHub: CVE-2026-26030 Microsoft Semantic Kernel InMemoryVectorStore filter functionality vulnerable
Microsoft Semantic Kernel InMemoryVectorStore filter functionality vulnerable to remote code execution
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| semantic-kernel | 0.0.1.dev0 ... 1.9.0 (126 versions) | 1.39.4 | — |
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
msrc
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26030
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.