Unauthenticated Directory Enumeration in InvokeAI

Executive Summary

CVE-2026-65012 is an unauthenticated directory enumeration vulnerability in InvokeAI versions before 6.13.7. It affects the GET /api/v2/models/scan_folder endpoint, which allows attackers to recursively enumerate arbitrary server filesystem directories by manipulating the scan_path parameter. Attackers can determine file existence and readability through HTTP response codes, bypassing multi-user mode access controls.

Useful 0 Not Useful 0

Detection Guidance

To detect this vulnerability, check if your InvokeAI instance is running a version prior to 6.13.7. Use commands like 'curl -X GET http://<target>/api/v2/models/scan_folder?scan_path=/etc' to test for directory enumeration. Monitor HTTP response codes (200 for readable paths, 400/500 for others) which indicate the vulnerability.

Additionally, inspect API responses for exposed sensitive files like invokeai.yaml or api_keys.yaml by accessing endpoints such as /api/v1/app/runtime_config without authentication.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows unauthenticated attackers to access sensitive files like invokeai.yaml and api_keys.yaml, which may contain API keys for image generation services and model download tokens. It also enables unauthorized access to administrator functions in multi-user mode and exposes sensitive credentials such as remote_api_tokens and external API keys.

• Attackers can enumerate filesystem paths and determine file existence and readability.
• Sensitive credentials and configuration details may be exposed to unauthorized users.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized access to sensitive files like api_keys.yaml and invokeai.yaml, which may contain API keys and tokens. Exposure of such data risks violating data protection requirements for confidentiality and access controls.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade InvokeAI to version 6.13.7 or later immediately. Rotate all API keys and tokens stored in configuration files like invokeai.yaml and api_keys.yaml. Ensure the application is not exposed to untrusted networks or the internet.

Restrict access to sensitive endpoints by implementing proper authentication and authorization controls. Avoid running InvokeAI in multi-user mode unless necessary and use strong passwords.

Useful 0 Not Useful 0