| Title | Microsoft AutoGen2(https://github.com/ag2ai/ag2 ≤ v0.13.4 Sandbox Issue |
|---|
| Description | AG2's classic `UserProxyAgent` code-execution path contains a two-stage issue:
1. the legacy `# filename:` header allows writes to attacker-chosen absolute paths instead of staying inside `work_dir`;
2. later `use_docker=True` executions decide whether they are "already inside Docker" only by checking `/.dockerenv`, which can be planted in stage 1.
As a result, if an attacker can influence message content delivered to `UserProxyAgent`, they can first create `/.dockerenv` and then cause later code execution to run in the current AG2 runtime environment instead of the expected temporary Docker execution container.
This is not `AssistantAgent` executing code by itself. `AssistantAgent` does not execute code by default. The problem is that its default prompt explicitly supports emitting code blocks with `# filename:`, and `UserProxyAgent` will treat such content as executable input. |
|---|
| Source | ⚠️ https://github.com/Ruoyyy/My_vulnerable/blob/main/report_legacy_filename_dockerenv_en.md |
|---|
| User | Ruoyyy (UID 78600) |
|---|
| Submission | 08/31/2026 09:51 (1 month ago) |
|---|
| Moderation | 10/10/2026 15:43 (1 month later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 416198 [ag2ai ag2 up to 0.13.4 UserProxyAgent os.path.join filename path traversal] |
|---|
| Points | 20 |
|---|