: Run the compilation process in a "jail" or isolated container so that even if an injection happens, the attacker can't access your host system.

If you're building an app that handles LaTeX, consider these defensive steps:

: Use a LaTeX Sanitizer to strip backslashes or dangerous keywords like \input , \include , and \write18 .

: If shell-escape is enabled, an attacker can run system commands like \write18{ls -la} to list files on the server.

: Using packages like listings to fetch internal files or hit internal network URLs. 🛠️ How to Stay Safe

🚀 LaTeX Injection - Payloads All The Things

: Using \input{/etc/passwd} to trick the server into printing the contents of its system files directly into a PDF.

: Ensure your LaTeX compiler is running with --no-shell-escape to prevent system-level command execution.