Advisory record · GHSA-vv9c-xxg7-wmv7

InvokeAI has External Control of File Name or Path

CVSS 9.8 CriticalCriticalEPSS 0.0040 · 34th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 18 Sept 2025, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
invokeaiPyPI<6.7.06.7.0
Identifiers
GHSA-vv9c-xxg7-wmv7 · CVE-2025-6237 · PYSEC-2026-359
Weakness (CWE)
CWE-22 · CWE-73
Published
18 Sept 2025
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

InvokeAI versions before 6.7.0 (PyPI package invokeai) contain a path traversal flaw in the bulk downloads API, which builds a filesystem path from a user-supplied name without proper validation. An unauthenticated remote attacker can exploit this to read arbitrary files outside the media directory and, depending on storage configuration, possibly overwrite or delete files. Upgrade to invokeai 6.7.0, which validates input paths and rejects traversal attempts.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.