| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A privilege escalation vulnerability exists in Rancher's impersonation middleware (pkg/auth/requests/impersonate.go). An authenticated Rancher user with the default user
global role can gain full administrative access to the Rancher control
plane and transitively to all downstream clusters it manages.
This issue affects Rancher: from 2.11.0 before 2.11.16, from 2.12.0 before 2.12.12, from 2.13.0 before 2.13.8, and from 2.14.0 before 2.14.2. |
| Rancher issues long-lived registration tokens to authenticate nodes and agents joining a downstream cluster. These tokens were stored and exposed in plaintext with no expiration, so a malicious user could obtain one either through the Rancher API, etcd, stored automation, or direct file access on a node, and could use it at any time to register a rogue node into the cluster. |
| Memory Corruption when processing registry values with incorrect types using a direct query method. |
| A vulnerability was found in heshengtao super-agent-party up to 0.4.1. This affects the function get_file_content of the file server.py of the component execute_tool_manually Endpoint. The manipulation of the argument tool_name/tool_params results in information disclosure. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way. |
| FrontMCP is a TypeScript-first framework for the Model Context Protocol (MCP). Prior to 1.5.7, the sandboxed codecall:execute tool exposes live host Zod schema instances to the script via getTool(), and because Zod v4 defines _zod as a non-configurable, non-writable own property, the ECMAScript Proxy invariants force the security membrane to hand back the raw host object, letting a script reach _zod.constr.constructor (the host Function constructor) and execute arbitrary code in the server process. A single tools/call is sufficient to escape the sandbox and achieve remote code execution as the server user, exposing everything the process holds such as OAuth client secrets, JWT_SECRET, session keys, database credentials, and cloud instance metadata. Because the framework's DEFAULT_AUTH_OPTIONS is public mode, an unconfigured server serves this to unauthenticated callers, and on authenticated servers an indirect prompt injection in tool output or fetched content can trigger it without a human attackerThis issue is fixed in version 1.5.7. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; never assigned. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
