An attacker can supply a malicious config.json file where the model_type field contains an injected newline character followed by arbitrary Python statements. When the model is loaded for training or inference, unsloth_compile_transformers() processes this configuration and passes the malicious input into an exec() call. This results in arbitrary code execution with the permissions of the user or service account performing the model load. This vulnerability impacts environments that load untrusted or externally sourced model configurations into Unsloth-based pipelines.

Impact

Successful exploitation allows for arbitrary code execution in the context of the user running the Unsloth framework. This could lead to full system compromise, exfiltration of sensitive model data, or persistence on the server hosting the training or inference environment.

Recommendation

Prioritized, concrete actions for detection engineering teams:

• Upgrade Unsloth Zoo to version 2026.8.14 or later, and Unsloth to versions beyond 2026.8.19, to incorporate the necessary input sanitization.
• Implement file integrity monitoring or scanning on model repositories to detect suspicious characters (e.g., newlines, import, exec, eval) within config.json files before they are processed by the training or inference pipeline.
• Run model-loading processes in isolated, low-privilege containers or sandboxes to limit the impact of potential RCE in the unsloth_compile_transformers() function.