14 matches found
CVE-2026-77523 MaxKB: Cross-workspace model parameter form write
MaxKB is an open-source AI assistant for enterprise. In version 2.10.3-lts and earlier, the model parameter form route authorizes the path workspace but ModelSerializer.ModelParams loads and saves a Model by id alone without including workspaceid in the query. An authenticated user with model rea...
CVE-2026-77523
MaxKB (an open-source enterprise AI assistant) is vulnerable to a cross-workspace model parameter form write in versions 2.10.3-lts and earlier . The root cause lies in the model parameter form route, which authorizes the path workspace, but ModelSerializer.ModelParams loads and saves a Model by ...
CVE-2026-77523 MaxKB: Cross-workspace model parameter form write
MaxKB is an open-source AI assistant for enterprise. In version 2.10.3-lts and earlier, the model parameter form route authorizes the path workspace but ModelSerializer.ModelParams loads and saves a Model by id alone without including workspaceid in the query. An authenticated user with model rea...
CVE-2026-59863 Kiota: Workspace-config poisoning: out-of-repo file write + generation-time SSRF
Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.5, Kiota honored a poisoned .kiota/workspace.json workspace configuration without validating per-client or per-plugin outputPath values during kiota client generate and kiota plugin generate, allowing a malicious...
CVE-2026-33989
Mobile Next is an MCP server for mobile development and automation. Prior to version 0.0.49, the @mobilenext/mobile-mcp server contains a Path Traversal vulnerability in the mobilesavescreenshot and mobilestartscreenrecording tools. The saveTo and output parameters were passed directly to...
EUVD-2025-24554
Malicious code in bioql PyPI...
CVE-2025-58373
Roo Code is an AI-powered autonomous coding agent that lives in users' editors. Versions 3.25.23 and below contain a vulnerability where .rooignore protections could be bypassed using symlinks. This allows an attacker with write access to the workspace to trick the extension into reading files th...
CVE-2025-55345
Using Codex CLI in workspace-write mode inside a malicious context repo, directory, etc could lead to arbitrary file overwrite and potentially remote code execution due to symlinks being followed outside the allowed current working directory...
CVE-2025-55345
Using Codex CLI in workspace-write mode inside a malicious context repo, directory, etc could lead to arbitrary file overwrite and potentially remote code execution due to symlinks being followed outside the allowed current working directory...
CVE-2025-55345 Unsafe symlink following in restricted workspace-write sandbox leads to RCE
Using Codex CLI in workspace-write mode inside a malicious context repo, directory, etc could lead to arbitrary file overwrite and potentially remote code execution due to symlinks being followed outside the allowed current working directory...
CVE-2025-55345
CVE-2025-55345 concerns OpenAI Codex CLI when used in a restricted workspace-write sandbox. The issue arises because symlinks are followed outside the allowed current working directory in a malicious context (repo/directory), enabling arbitrary file overwrite and potentially remote code execution...
CVE-2025-55345
Using Codex CLI in workspace-write mode inside a malicious context repo, directory, etc could lead to arbitrary file overwrite and potentially remote code execution due to symlinks being followed outside the allowed current working directory...
PT-2025-32971 · Codex Cli · Codex Cli
Name of the Vulnerable Software and Affected Versions: Codex CLI affected versions not specified Description: Using Codex CLI in workspace-write mode within a malicious context repository, directory, etc. may lead to arbitrary file overwrite and potentially remote code execution. This occurs...
CVE-2025-55345: UNIX Symbolic Link (Symlink) Following
Using Codex CLI in workspace-write mode inside a malicious context repo, directory, etc could lead to arbitrary file overwrite and potentially remote code execution due to symlinks being followed outside the allowed current working directory...