VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

semantic-kernel: vulnerability history, versions and safety

semantic-kernel is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 108 releases, from Feb 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all semantic-kernel vulnerabilities

Vulert verdict on semantic-kernel 1.45.0 i

Updated on 23 Oct 2026

Good news: 1.45.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 81/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 1.45.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.45.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.45.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Depended on by 26 packages i
  • Stars 28,677 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for semantic-kernel, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.45.0 06 Oct 2026 none MIT — Details →
1.44.1 06 Aug 2026 none MIT — Details →
1.44.0 07 Jul 2026 none MIT — Details →
1.43.1 17 Jun 2026 none MIT — Details →
1.43.0 03 Jun 2026 none MIT — Details →
1.42.0 14 May 2026 none MIT — Details →
1.41.3 28 Apr 2026 none MIT — Details →
1.41.2 08 Apr 2026 none MIT — Details →
1.41.1 25 Mar 2026 none MIT — Details →
1.41.0 13 Mar 2026 none MIT — Details →
1.40.0 02 Mar 2026 none MIT — Details →
1.39.4 10 Feb 2026 none MIT — Details →
1.39.3 02 Feb 2026 C1 U1 MIT Yes Details →
1.39.2 19 Jan 2026 C1 U2 MIT Yes Details →
1.39.1 15 Jan 2026 C1 U2 MIT Yes Details →
1.39.0 26 Nov 2025 C1 U2 MIT Yes Details →
1.38.0 11 Nov 2025 C1 U2 MIT Yes Details →
1.37.1 30 Oct 2025 C1 U2 MIT Yes Details →
1.37.0 16 Sep 2025 C1 U2 MIT Yes Details →
1.36.2 04 Sep 2025 C1 U2 MIT Yes Details →
1.36.1 02 Sep 2025 C1 U2 MIT Yes Details →
1.36.0 27 Aug 2025 C1 U2 MIT Yes Details →
1.35.3 14 Aug 2025 C1 U2 MIT Yes Details →
1.35.2 08 Aug 2025 C1 U2 MIT Yes Details →
1.35.1 05 Aug 2025 C1 U2 MIT Yes Details →
1.35.0 16 Jul 2025 C1 U2 MIT Yes Details →
1.34.0 25 Jun 2025 C1 U2 MIT Yes Details →
1.33.0 10 Jun 2025 C1 U2 MIT Yes Details →
1.32.2 04 Jun 2025 C1 U2 MIT Yes Details →
1.32.1 03 Jun 2025 C1 U2 MIT Yes Details →
1.32.0 28 May 2025 C1 U2 MIT Yes Details →
1.31.0 20 May 2025 C1 U2 MIT Yes Details →
1.30.0 15 May 2025 C1 U2 MIT Yes Details →
1.29.0 28 Apr 2025 C1 U2 MIT Yes Details →
1.28.1 17 Apr 2025 C1 U2 MIT Yes Details →
1.28.0 11 Apr 2025 C1 U2 MIT Yes Details →
1.27.2 07 Apr 2025 C1 U2 MIT Yes Details →
1.27.1 04 Apr 2025 C1 U2 MIT Yes Details →
1.27.0 03 Apr 2025 C1 U2 MIT Yes Details →
1.26.1 25 Mar 2025 C1 U2 MIT Yes Details →
1.26.0 25 Mar 2025 C1 U2 MIT Yes Details →
1.25.0 18 Mar 2025 C1 U2 MIT Yes Details →
1.24.1 13 Mar 2025 C1 U2 MIT Yes Details →
1.24.0 11 Mar 2025 C1 U2 MIT Yes Details →
1.23.1 07 Mar 2025 C1 U2 MIT Yes Details →
1.23.0 06 Mar 2025 C1 U2 MIT Yes Details →
1.22.1 03 Mar 2025 C1 U2 MIT Yes Details →
1.22.0 28 Feb 2025 C1 U2 MIT Yes Details →
1.21.3 19 Feb 2025 C1 U2 MIT Yes Details →
1.21.2 19 Feb 2025 C1 U2 MIT Yes Details →
1.21.1 14 Feb 2025 C1 U2 MIT Yes Details →
1.21.0 12 Feb 2025 C1 U2 MIT Yes Details →
1.20.0 29 Jan 2025 C1 U2 MIT Yes Details →
1.19.0 22 Jan 2025 C1 U2 MIT Yes Details →
1.18.2 13 Jan 2025 C1 U2 MIT Yes Details →
1.18.1 09 Jan 2025 C1 U2 MIT Yes Details →
1.18.0 07 Jan 2025 C1 U2 MIT Yes Details →
1.17.1 19 Dec 2024 C1 U2 MIT Yes Details →
1.17.0 05 Dec 2024 C1 U2 MIT Yes Details →
1.16.0 21 Nov 2024 C1 U2 MIT Yes Details →
1.15.0 15 Nov 2024 C1 U2 MIT Yes Details →
1.14.0 07 Nov 2024 C1 U2 MIT Yes Details →
1.13.0 31 Oct 2024 C1 U2 MIT Yes Details →
1.12.1 25 Oct 2024 C1 U2 MIT Yes Details →
1.12.0 24 Oct 2024 C1 U2 MIT Yes Details →
1.11.0 02 Oct 2024 C1 U2 MIT Yes Details →
1.10.1 30 Sep 2024 C1 U2 MIT Yes Details →
1.10.0 26 Sep 2024 C1 U2 MIT Yes Details →
1.9.0 16 Sep 2024 C1 U2 MIT Yes Details →
1.8.3 06 Sep 2024 C1 U2 MIT Yes Details →
1.8.2 28 Aug 2024 C1 U2 MIT Yes Details →
1.8.1 28 Aug 2024 C1 U2 — Yes Details →
1.8.0 22 Aug 2024 C1 U2 — Yes Details →
1.7.0 21 Aug 2024 C1 U2 — Yes Details →
1.6.0 20 Aug 2024 C1 U2 — Yes Details →
1.5.1 14 Aug 2024 C1 U2 — Yes Details →
1.5.0 07 Aug 2024 C1 U2 — Yes Details →
1.4.0 05 Aug 2024 C1 U2 — Yes Details →
1.3.0 23 Jul 2024 C1 U2 — Yes Details →
1.2.0 09 Jul 2024 C1 U2 — Yes Details →
1.1.2 24 Jun 2024 C1 U2 — Yes Details →
1.1.1 15 Jun 2024 C1 U2 — Yes Details →
1.1.0 13 Jun 2024 C1 U2 — Yes Details →
1.0.5 05 Jun 2024 C1 U2 — Yes Details →
1.0.4 03 Jun 2024 C1 U2 — Yes Details →
1.0.3 28 May 2024 C1 U2 — Yes Details →
1.0.2 23 May 2024 C1 U2 — Yes Details →
1.0.1 22 May 2024 C1 U2 — Yes Details →
1.0.0 21 May 2024 C1 U2 — Yes Details →
1.0.0rc1 17 May 2024 C1 U2 — Yes Details →
0.9.9b1 16 May 2024 C1 U2 — Yes Details →
0.9.8b1 09 May 2024 C1 U2 — Yes Details →
0.9.7b1 06 May 2024 C1 U2 — Yes Details →
0.9.6b1 16 Apr 2024 C1 U2 — Yes Details →
0.9.5b1 01 Apr 2024 C1 U2 — Yes Details →
0.9.4b1 20 Mar 2024 C1 U2 — Yes Details →
0.9.3b1 15 Mar 2024 C1 U2 — Yes Details →
0.9.2b1 13 Mar 2024 C1 U2 — Yes Details →
0.9.1b1 08 Mar 2024 C1 U2 — Yes Details →
0.9.0b1 04 Mar 2024 C1 U2 — Yes Details →
0.5.1.dev0 09 Feb 2024 C1 U2 — Yes Details →
0.5.0.dev0 01 Feb 2024 C1 U2 — Yes Details →
0.4.7.dev0 26 Jan 2024 C1 U2 — Yes Details →
0.4.6.dev0 23 Jan 2024 C1 U2 — Yes Details →
0.4.5.dev0 11 Jan 2024 C1 U2 — Yes Details →
0.4.4.dev0 05 Jan 2024 C1 U2 — Yes Details →
0.4.3.dev0 15 Dec 2023 C1 U2 — Yes Details →
0.4.2.dev0 12 Dec 2023 C1 U2 — Yes Details →
0.4.1.dev0 05 Dec 2023 C1 U2 — Yes Details →
0.4.0.dev0 29 Nov 2023 C1 U2 — Yes Details →
0.3.15.dev0 15 Nov 2023 C1 U2 — Yes Details →
0.3.14.dev0 23 Oct 2023 C1 U2 — Yes Details →
0.3.13.dev0 18 Sep 2023 C1 U2 — Yes Details →
0.3.12.dev0 11 Sep 2023 C1 U2 — Yes Details →
0.3.11.dev0 06 Sep 2023 C1 U2 — Yes Details →
0.3.10.dev0 28 Aug 2023 C1 U2 — Yes Details →
0.3.9.dev0 23 Aug 2023 C1 U2 — Yes Details →
0.3.8.dev0 10 Aug 2023 C1 U2 — Yes Details →
0.3.7.dev0 08 Aug 2023 C1 U2 — Yes Details →
0.3.6.dev0 07 Aug 2023 C1 U2 — Yes Details →

The newest 120 of 138 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for semantic-kernel

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-26030: Microsoft Semantic Kernel InMemoryVectorStore Remote Code Execution Vulnerability 9.9 critical 1.39.4 19 Feb 2026
CVE-2026-26030: Remote Code Execution Vulnerability in Semantic Kernel Python SDK 9.9 critical 1.39.4 19 Feb 2026
CVE-2026-25592: Semantic Kernel .NET SDK Arbitrary File Write Vulnerability 9.9 critical 1.39.3 29 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About semantic-kernel

Is semantic-kernel safe to use?

Vulert records 3 vulnerabilities for semantic-kernel in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is semantic-kernel's Vulert package health score?

Vulert scores semantic-kernel 81/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of semantic-kernel affected?

No. 1.45.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of semantic-kernel should I use?

1.45.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does semantic-kernel have?

3 vulnerabilities are recorded for semantic-kernel in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new semantic-kernel vulnerabilities disclosed?

3 vulnerabilities were recorded for semantic-kernel in the last 12 months, and the oldest entry in this database dates to 19 Feb 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of semantic-kernel are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor semantic-kernel for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the semantic-kernel version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.