Security Digest · Vulnerability record

CVE-2024-11042: InvokeAI Arbitrary File Deletion vulnerability

In invoke-ai/invokeai version v5.0.2, the web API POST /api/v1/images/delete is vulnerable to Arbitrary File Deletion.

CVSS 9.1 Critical EPSS 1.6% · p75

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 1.6%, percentile 75: FIRST’s model estimates a 1.6% chance of exploitation activity in the next 30 days, higher than 75% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes InvokeAI (PyPI) < 5.3.0rc1, fixed in 5.3.0rc1. Check your lockfile, including transitive dependencies.

What it is

In invoke-ai/invokeai version v5.0.2, the web API POST /api/v1/images/delete is vulnerable to Arbitrary File Deletion. This vulnerability allows unauthorized attackers to delete arbitrary files on the server, potentially including critical or sensitive system files such as SSH keys, SQLite databases, and configuration files. This can impact the integrity and availability of applications relying on these files.

From the GitHub advisory

In invoke-ai/invokeai version v5.0.2, the web API POST /api/v1/images/delete is vulnerable to Arbitrary File Deletion. This vulnerability allows unauthorized attackers to delete arbitrary files on the server, potentially including critical or sensitive system files such as SSH keys, SQLite databases, and configuration files. This can impact the integrity and availability of applications relying on these files.

Weakness type: CWE-73, CWE-20, CWE-22.

Product: InvokeAI (PyPI) · Assigned by: @huntr_ai · Published: 2025-03-20

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIInvokeAI< 5.3.0rc15.3.0rc1
VendorProductAffected versions (per CVE record)
invoke-aiinvoke-ai/invokeaiunspecified < 5.3.0

Severity scores

Scored byCVSSScoreVector
@huntr_ai3.09.1 CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
GitHub3.19.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 1.56% probability of exploitation activity in the next 30 days; percentile 75.

Timeline

  • — CVE record published by @huntr_ai
  • — GitHub-reviewed advisory GHSA-227r-w5j2-6243 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-227r-w5j2-6243 github.com
  2. CVE.org record CVE-2024-11042 cve.org
  3. NVD entry CVE-2024-11042 nvd.nist.gov

Other references from the CVE record and advisory

  1. huntr.com huntr.com
  2. github.com github.com

Critical PyPI advisories · Today’s Security Digest