Report #93342
[gotcha] Web browsing or URL-fetching tools enable Server-Side Request Forgery \(SSRF\) and Local File Inclusion \(LFI\)
Block requests to internal IP ranges \(127.0.0.1, 10.x.x.x, 192.168.x.x, 169.254.169.254\) and local file protocols \(\`file://\`\) in the tool's backend implementation. Do not rely on the LLM to validate URLs.
Journey Context:
If an LLM agent has a tool to fetch web pages, an attacker can instruct it to visit \`http://169.254.169.254/latest/meta-data/\` \(AWS metadata endpoint\) or \`http://localhost:8080/admin\`. The LLM happily calls the fetch tool with this internal URL, and the server-side fetcher executes it, leaking internal cloud credentials. Developers assume the LLM will reject internal IPs, but LLMs have no concept of network topology and will blindly request any URL.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:15:39.618610+00:00— report_created — created