Akshatgit

#5569de 55,133
49.5CVSS total
Vulnerabilidades · 6
Média
1
Alta
2
Crítica
3
PT-2026-50139
8.8
2026-06-16
Langflow · Langflow · CVE-2026-33760
**Nome do Software Vulnerável e Versões Afetadas** Langflow versões anteriores a 1.9.0 **Description** O roteador `/api/v1/monitor` expõe sete endpoints que permitem operações de leitura, gravação e exclusão em recursos de propriedade do usuário, incluindo mensagens, sessões, artefatos de build e logs de transações de LLM. O sistema não verifica se o solicitante autenticado é o proprietário do recurso solicitado, resultando em uma Referência Direta Insegura a Objeto (IDOR), também conhecida como Broken Object Level Authorization (BOLA). Um usuário autenticado pode ler, modificar, renomear ou excluir permanentemente os dados de outro usuário ao fornecer o ID do recurso ou o `flow id` do alvo. Detalhes técnicos incluem os seguintes endpoints vulneráveis: - 'GET /api/v1/monitor/builds' e 'DELETE /api/v1/monitor/builds' utilizando a variável `flow id`. - 'DELETE /api/v1/monitor/messages' utilizando a variável `message ids`. - 'PUT /api/v1/monitor/messages/{message id}' utilizando a variável `message id`. - 'PATCH /api/v1/monitor/messages/session/{old session id}' utilizando a variável `old session id`. - 'DELETE /api/v1/monitor/messages/session/{session id}' utilizando a variável `session id`. - 'GET /api/v1/monitor/transactions' utilizando a variável `flow id`. **Recommendations** Atualize para a versão 1.9.0. Como medida paliativa temporária, restrinja o acesso aos endpoints `/api/v1/monitor` para minimizar o risco de acesso ou exclusão não autorizada de dados.
PT-2026-28381
4.3
2026-03-26
Unknown · Open-Webui · CVE-2026-28786
**Name of the Vulnerable Software and Affected Versions** Open WebUI versions prior to 0.8.6 **Description** Open WebUI is a self-hosted artificial intelligence platform designed for offline operation. A flaw exists in the speech-to-text transcription endpoint where an unsanitized filename field allows any authenticated, non-admin user to trigger a `FileNotFoundError`. The error message, including the server's absolute `DATA DIR` path, is then returned in the HTTP 400 response body, leading to information disclosure on default deployments. The issue stems from a lack of path sanitization when extracting the file extension from the filename and constructing the file path. Specifically, the `file.filename.split(".")[-1]` function is used without any sanitization, and the resulting value is concatenated into a filesystem path. This allows an attacker to craft a filename containing directory traversal sequences (e.g., `audio./etc/passwd`) to reveal the server's absolute path. The vulnerability is present in the `backend/open webui/routers/audio.py` file, at line 1197, and is triggered when attempting to open a file with a malicious filename. The MIME-type guard does not prevent this issue. **Recommendations** Versions prior to 0.8.6 should be updated to version 0.8.6 or later to address the issue. As a temporary workaround, consider sanitizing the file extension using `Path(file.filename).name` and suppressing the internal path in error responses. Restrict access to the audio transcription endpoint to minimize the risk of exploitation.
PT-2026-26336
9.9
2026-03-19
Langflow · Langflow · CVE-2026-33309
**Name of the Vulnerable Software and Affected Versions** Langflow versions 1.2.0 through 1.8.1 **Description** Langflow, a tool for building and deploying AI-powered agents and workflows, contains a security flaw that allows authenticated attackers to write files anywhere on the host system, potentially leading to Remote Code Execution (RCE). The root architectural issue within `LocalStorageService` remains unresolved due to a lack of boundary containment checks in the underlying storage layer. The system relies entirely on the HTTP-layer `ValidatedFileName` dependency, which fails to protect against this issue. Specifically, the `POST /api/v2/files/` endpoint is vulnerable because the multipart upload filename bypasses the path-parameter guard. The vulnerability exists in two layers: the API layer (`src/backend/base/langflow/api/v2/files.py:162`) and the storage layer (`src/backend/base/langflow/services/storage/local.py:114-116`). The filename is extracted directly from the multipart `Content-Disposition` header and used in naive path concatenation without proper validation. A proof-of-concept demonstrates the ability to write a file outside the user's storage directory using directory traversal techniques. Successful exploitation could allow attackers to overwrite critical system files, inject malicious Python components, or compromise the system's security. **Recommendations** Langflow versions prior to 1.9.0 are affected. Update to version 1.9.0 to resolve the vulnerability.