langflow: /profile_pictures/{folder_name}/{file_name} Endpunkt-Datei-Lesen

The vulnerability lies within the downloadprofilepicture function, where user-supplied path components are directly concatenated without proper validation. An attacker can craft malicious requests containing traversal sequences like ../secret_key to navigate the filesystem beyond the designated profile pictures directory. This could lead to the exposure of sensitive configuration files, API keys, or other critical data stored on the server. The potential blast radius extends to any data accessible by the web server process, depending on its permissions.

Organizations utilizing Langflow for AI agent development and deployment are at risk, particularly those running versions prior to 1.7.1. This includes teams relying on Langflow's profile picture functionality and those who have not implemented robust file access controls. Shared hosting environments where multiple users share the same Langflow instance are also at increased risk.

• python / server:

import os
import re

def check_langflow_secret_key(log_file):
    with open(log_file, 'r') as f:
        for line in f:
            if re.search(r'secret_key=', line):
                return True
    return False

# Example usage:
log_file = '/path/to/langflow/logs/error.log'
if check_langflow_secret_key(log_file):
    print('Potential secret_key exposure detected!')
else:
    print('No secret_key exposure detected.')

• generic web:

curl -I 'http://your-langflow-instance/profile_pictures/../../../../secret_key' # Check for directory traversal

1. 2026-03-20Disclosure

   disclosure

1. Reserviert2026-03-20
2. Veröffentlicht2026-03-20
3. Geändert2026-03-27
4. EPSS aktualisiert2026-04-01

The primary mitigation is to upgrade Langflow to version 1.7.1 or later, which includes the necessary sanitization and validation to prevent path traversal. As a temporary workaround, restrict access to the /api/v1/files/profilepictures/{foldername}/{filename} endpoint using a Web Application Firewall (WAF) or proxy. Implement strict input validation on both foldername and file_name parameters, ensuring they only contain alphanumeric characters and prevent the use of traversal sequences. Consider implementing a chroot jail to limit the web server's access to specific directories.