VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

invokeai: vulnerability history, versions and safety

invokeai is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 120 releases, from Mar 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded C2 H3 U5
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all invokeai vulnerabilities

Vulert verdict on invokeai 6.14.2 i

Updated on 23 Oct 2026

Careful: 6.14.2 has 6 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.14.2 — affected i
  • Vulnerabilities on record 10 over 1 year · 4 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Stars 28,646 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 invokeai, 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
7.0.0a3 19 Oct 2026 H3 U3 non-standard No Details →
7.0.0a2 11 Oct 2026 H3 U3 non-standard No Details →
7.0.0a1 04 Oct 2026 H3 U3 non-standard No Details →
6.14.2 27 Sep 2026 H3 U3 non-standard No Details →
6.14.1 06 Sep 2026 H3 U3 non-standard No Details →
6.14.0 25 Aug 2026 H3 U3 non-standard No Details →
6.14.0rc2 16 Aug 2026 H3 U3 non-standard No Details →
6.13.8 13 Aug 2026 H3 U3 non-standard No Details →
6.14.0rc1 31 Jul 2026 H3 U3 non-standard No Details →
6.13.7 21 Jul 2026 H3 U3 non-standard No Details →
6.13.6 05 Jul 2026 H3 U3 non-standard No Details →
6.13.5 04 Jul 2026 H3 U3 non-standard No Details →
6.13.5rc1 30 Jun 2026 H3 U3 non-standard No Details →
6.13.0 27 May 2026 H3 U3 non-standard No Details →
6.13.0rc3 16 May 2026 H3 U3 non-standard No Details →
6.13.0rc2 09 May 2026 H3 U3 non-standard No Details →
6.13.0rc1 30 Apr 2026 H3 U3 non-standard No Details →
6.12.0 22 Mar 2026 H3 U3 non-standard No Details →
6.12.0rc1 09 Mar 2026 H3 U3 non-standard No Details →
6.11.1 06 Feb 2026 H3 U3 non-standard No Details →
6.11.0 31 Jan 2026 H3 U3 non-standard No Details →
6.11.0rc1 27 Jan 2026 H3 U3 non-standard No Details →
6.10.0 06 Jan 2026 H3 U3 non-standard No Details →
6.10.0rc2 04 Jan 2026 H3 U3 non-standard No Details →
6.10.0rc1 26 Dec 2025 H3 U3 non-standard No Details →
6.9.0 17 Oct 2025 H3 U3 non-standard No Details →
6.9.0rc3 15 Oct 2025 H3 U3 non-standard No Details →
6.9.0rc2 15 Oct 2025 H3 U3 non-standard No Details →
6.9.0rc1 15 Oct 2025 H3 U3 non-standard No Details →
6.9.0a3 14 Oct 2025 H3 U3 non-standard No Details →
6.9.0a2 12 Oct 2025 H3 U3 non-standard No Details →
6.8.1 12 Oct 2025 H3 U3 non-standard No Details →
6.9.0a1 10 Oct 2025 H3 U3 non-standard No Details →
6.8.0 08 Oct 2025 H3 U3 non-standard No Details →
6.8.0rc2 08 Oct 2025 H3 U3 non-standard No Details →
6.8.0rc1 17 Sep 2025 H3 U3 non-standard No Details →
6.7.0 15 Sep 2025 H3 U3 non-standard No Details →
6.7.0rc1 11 Sep 2025 U1 non-standard Yes Details →
6.6.0 08 Sep 2025 U1 non-standard Yes Details →
6.6.0rc2 04 Sep 2025 U1 non-standard Yes Details →
6.6.0rc1 03 Sep 2025 U1 non-standard Yes Details →
6.5.1 28 Aug 2025 U1 non-standard Yes Details →
6.5.0 28 Aug 2025 U1 non-standard Yes Details →
6.5.0rc1 25 Aug 2025 U1 non-standard Yes Details →
6.4.0 19 Aug 2025 U1 non-standard Yes Details →
6.4.0rc2 18 Aug 2025 U1 non-standard Yes Details →
6.4.0rc1 15 Aug 2025 U1 non-standard Yes Details →
6.3.0 05 Aug 2025 U1 non-standard Yes Details →
6.3.0rc2 04 Aug 2025 U1 non-standard Yes Details →
6.3.0rc1 31 Jul 2025 U1 non-standard Yes Details →
6.3.0a1 25 Jul 2025 U1 non-standard Yes Details →
6.2.0 25 Jul 2025 U1 non-standard Yes Details →
6.1.0 21 Jul 2025 U1 non-standard Yes Details →
6.1.0rc2 18 Jul 2025 U1 non-standard Yes Details →
6.1.0rc1 17 Jul 2025 U1 non-standard Yes Details →
6.0.2 12 Jul 2025 U1 non-standard Yes Details →
6.0.1 12 Jul 2025 U1 non-standard Yes Details →
6.0.1rc1 10 Jul 2025 U1 non-standard Yes Details →
6.0.0 09 Jul 2025 U1 non-standard Yes Details →
6.0.0rc5 08 Jul 2025 U1 non-standard Yes Details →
6.0.0rc4 07 Jul 2025 U1 non-standard Yes Details →
6.0.0rc3 04 Jul 2025 U1 non-standard Yes Details →
6.0.0rc2 03 Jul 2025 U1 non-standard Yes Details →
6.0.0rc1 01 Jul 2025 U1 non-standard Yes Details →
6.0.0a10 26 Jun 2025 U1 non-standard Yes Details →
6.0.0a8 25 Jun 2025 U1 non-standard Yes Details →
6.0.0a6 24 Jun 2025 U1 non-standard Yes Details →
6.0.0a5 23 Jun 2025 U1 non-standard Yes Details →
6.0.0a4 20 Jun 2025 U1 non-standard Yes Details →
6.0.0a3 20 Jun 2025 U1 non-standard Yes Details →
5.15.0 16 Jun 2025 H1 U1 non-standard No Details →
6.0.0a2 16 Jun 2025 U1 non-standard Yes Details →
6.0.0a1 10 Jun 2025 H1 U1 non-standard No Details →
5.14.0 06 Jun 2025 H1 U1 non-standard No Details →
5.13.0 04 Jun 2025 H1 U1 non-standard No Details →
5.13.0rc3 30 May 2025 H1 U1 non-standard No Details →
5.13.0rc2 30 May 2025 H1 U1 non-standard No Details →
5.13.0rc1 27 May 2025 H1 U1 non-standard No Details →
5.12.0 22 May 2025 H1 U1 non-standard No Details →
5.12.0rc2 21 May 2025 H1 U1 non-standard No Details →
5.12.0rc1 19 May 2025 H1 U1 non-standard No Details →
5.11.0 13 May 2025 H1 U1 non-standard No Details →
5.11.0rc2 05 May 2025 H1 U1 non-standard No Details →
5.11.0rc1 28 Apr 2025 H1 U1 non-standard No Details →
5.10.1 19 Apr 2025 H1 U1 non-standard No Details →
5.10.0 17 Apr 2025 H1 U1 non-standard No Details →
5.10.0rc1 15 Apr 2025 H1 U1 non-standard No Details →
5.10.0a1 08 Apr 2025 H1 U1 non-standard No Details →
5.10.0.dev4 04 Apr 2025 H1 U1 non-standard No Details →
5.10.0.dev3 04 Apr 2025 H1 U1 non-standard No Details →
5.10.0.dev2 03 Apr 2025 H1 U1 non-standard No Details →
5.10.0.dev1 02 Apr 2025 H1 U1 non-standard No Details →
5.9.1 31 Mar 2025 H1 U1 non-standard No Details →
5.9.0 26 Mar 2025 H1 U1 non-standard No Details →
5.9.0rc2 24 Mar 2025 H1 U1 non-standard No Details →
5.9.0rc1 21 Mar 2025 H1 U1 non-standard No Details →
5.8.1 17 Mar 2025 H1 U1 non-standard No Details →
5.8.0 17 Mar 2025 H1 U1 non-standard No Details →
5.8.0rc1 13 Mar 2025 H1 U1 non-standard No Details →
5.8.0a2 11 Mar 2025 H1 U1 non-standard No Details →
5.8.0a1 07 Mar 2025 H1 U1 — No Details →
5.7.2 05 Mar 2025 H1 U1 — No Details →
5.7.2rc2 03 Mar 2025 H1 U1 — No Details →
5.7.2rc1 02 Mar 2025 H1 U1 — No Details →
5.7.1 28 Feb 2025 H1 U1 — No Details →
5.7.0 27 Feb 2025 H1 U1 — No Details →
5.7.0rc2 26 Feb 2025 H1 U1 — No Details →
5.7.0rc1 21 Feb 2025 H1 U1 — No Details →
5.7.0a1 16 Feb 2025 H1 U1 — No Details →
5.6.2 14 Feb 2025 H1 U1 — No Details →
5.6.1 11 Feb 2025 H1 U1 — No Details →
5.6.1rc1 06 Feb 2025 H1 U1 — No Details →
5.6.0 21 Jan 2025 H1 U1 — No Details →
5.6.0rc4 17 Jan 2025 H1 U1 — No Details →
5.6.0rc3 17 Jan 2025 H1 U1 — No Details →
5.6.0rc2 09 Jan 2025 H1 U1 — No Details →
5.6.0rc1 07 Jan 2025 H1 U1 — No Details →
5.5.0 20 Dec 2024 H1 U1 — No Details →
5.5.0rc1 19 Dec 2024 H1 U1 — No Details →
5.4.4rc1 18 Dec 2024 H1 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 6
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for invokeai

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-12029: InvokeAI Remote Code Execution via Unsafe Deserialization 9.8 critical 5.4.3rc2 21 Mar 2025
CVE-2025-6237: InvokeAI Path Traversal and Arbitrary File Deletion Vulnerability 9.8 high No fix published 18 Sep 2025
CVE-2025-6237: InvokeAI Path Traversal Vulnerability Allows Unauthorized File Access 9.8 critical 6.7.0 29 Jun 2026
CVE-2024-11042: InvokeAI Arbitrary File Deletion Vulnerability 9.1 critical 5.3.0rc1 20 Mar 2025
CVE-2024-11042: InvokeAI Arbitrary File Deletion Vulnerability 9.1 critical 5.3.0rc1 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 invokeai

Is invokeai safe to use?

Vulert records 10 vulnerabilities for invokeai in PyPI: 2 critical, 3 high, 0 medium and 0 low, plus 5 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is invokeai's Vulert package health score?

Vulert scores invokeai 50/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of invokeai affected?

Yes. 6.14.2, the version you would install today, has 6 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of invokeai should I use?

6.14.2 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 invokeai have?

10 vulnerabilities are recorded for invokeai in the PyPI ecosystem: 2 critical, 3 high, 0 medium and 0 low, plus 5 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 invokeai vulnerabilities disclosed?

4 vulnerabilities were recorded for invokeai in the last 12 months, and the oldest entry in this database dates to 20 Mar 2025. 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 invokeai 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 invokeai for upcoming vulnerabilities?

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