Unsloth Watch posted an update
Unsloth has added a guard against unsafe loading of PyTorch .pt2 archives, changing how specific torch.export loading paths handle pickle data. The project’s commit says crafted archives could run code when loaded, and identifies PyTorch versions 2.6 to 2.14 as affected.
Why it mattersThe guard forces weightsonly=True in the relevant export-loader paths and blocks a pickle.loads route inside torch.export.pt2archive.package. Unsloth says ordinary exported programs and other torch.load callers are unchanged. An environment variable can restore the previous behaviour, so operators should check the commit’s details before relying on the safeguard.
Discuss: Should libraries quietly enforce safer loading defaults, or should users have to opt in when that could change compatibility?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.