# CVE-2025-6237: InvokeAI has External Control of File Name or Path

Source: https://junglewise.ai/threats/cve-2025-6237-invokeai-has-external-control-of-file-name-or-path  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-09-18  
License: CC BY 4.0 with a link back

CVE-2025-6237 · Severity: critical · CVSS 9.8 · Published 2025-09-18

### Path Traversal Vulnerability in InvokeAI

A path traversal vulnerability in **InvokeAI** (versions < 6.7.0) allows an unauthenticated remote attacker to read files outside the intended media directory via the **bulk downloads** API.

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.

**Affected versions:** `< 6.7.0`
**Patched version:** `6.7.0`

Technologies: [invokeai (PyPI)](https://junglewise.ai/threats/technologies/pypi-invokeai). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2025-6237 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-6237 being exploited in the wild.

**How severe is CVE-2025-6237?** Critical severity, with a CVSS score of 9.8, published 18 September 2025.

**Which products and versions are affected?** invokeai (PyPI) < 6.7.0, ECOSYSTEM:introduced=0,fixed=6.7.0.

**Is there a fix for CVE-2025-6237?** Yes. invokeai (PyPI): upgrade to 6.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-6237?** Check whether you run invokeai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- invokeai (PyPI): upgrade to 6.7.0 or later

  ```sh
  pip install "invokeai>=6.7.0"
  ```


## Affected products

- invokeai (PyPI) < 6.7.0, ECOSYSTEM:introduced=0,fixed=6.7.0

## Identifiers

- CVE-2025-6237
- GHSA-vv9c-xxg7-wmv7
- PYSEC-2026-359

## Related threats

- [PYSEC-2026-1467 - InvokeAI Uncontrolled Resource Consumption vulnerability](https://junglewise.ai/threats/cve-2024-11043-invokeai-uncontrolled-resource-consumption-vulnerability)
- [PYSEC-2026-1466 - InvokeAI has Denial of Service (DoS) vulnerability in `/api/v1/images/upload`](https://junglewise.ai/threats/cve-2024-10821-invokeai-has-denial-of-service-dos-vulnerability-in-api-v1-images)
- [InvokeAI Arbitrary File Deletion vulnerability](https://junglewise.ai/threats/cve-2024-11042-invokeai-arbitrary-file-deletion-via-directory-traversal)
- [InvokeAI Deserialization of Untrusted Data vulnerability](https://junglewise.ai/threats/cve-2024-12029-invokeai-deserialization-of-untrusted-data-vulnerability)