Security Digest · Vulnerability record
CVE-2025-6237: InvokeAI has External Control of File Name or Path
A vulnerability in invokeai version v6.0.0a1 and below allows attackers to perform path traversal and arbitrary file deletion via the GET /api/v1/images/download/{bulkdownloaditemname} endpoint.
CVSS 9.3 Critical EPSS 0.4% · p31
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 0.4%, percentile 31: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 31% of all scored CVEs (low). 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) < 6.7.0, fixed in 6.7.0. Check your lockfile, including transitive dependencies.
What it is
A vulnerability in invokeai version v6.0.0a1 and below allows attackers to perform path traversal and arbitrary file deletion via the GET /api/v1/images/download/{bulkdownloaditemname} endpoint. By manipulating the filename arguments, attackers can read and delete any files on the server, including critical system files such as SSH keys, databases, and configuration files. This vulnerability results in high confidentiality, integrity, and availability impacts.
From the GitHub advisory
Path Traversal Vulnerability in InvokeAI
A path traversal vulnerability in InvokeAI (versions
The endpoint accepts a user-controlled file/item name and concatenates it into a filesystem path without proper canonicalization or allow-listing. By supplying sequences such as ../ (or absolute paths), an attacker can cause the server to traverse directories and return arbitrary files.
In certain storage or back-end configurations, abusing attacker-controlled paths can also lead to unintended overwriting or deletion of files referenced by the crafted path.
The issue is fixed in 6.7.0, which normalizes and validates input paths and rejects traversal attempts.
Weakness type: CWE-73, CWE-22.
Product: invokeai (PyPI) · Assigned by: @huntr_ai · Published: 2025-09-18
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | invokeai | < 6.7.0 | 6.7.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| invoke-ai | invoke-ai/invokeai | unspecified <= latest |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.8 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
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 total.
- FIRST EPSS (model of 2026-10-21): 0.39% probability of exploitation activity in the next 30 days; percentile 31.
Timeline
- — CVE record last updated
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-vv9c-xxg7-wmv7 published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-vv9c-xxg7-wmv7 github.com
- CVE.org record CVE-2025-6237 cve.org
- NVD entry CVE-2025-6237 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- github.com github.com
- github.com github.com