Repository navigation
require opt-in to access the pickle codec #4404
Description
the pickle codec is useful but also a huge security hole, since it allows arbitrary code execution based on encoded data. opening data encoded with the pickle codec should probably fail unless the user has explicitly opted in to accessing the unsafe codec, e.g. via an environment variable and runtime configuration setting.
Reacted by Chris Holden
Activity
bhaskargurram-ai commentedon Oct 2, 2026
I'd like to work on this. My plan is a config option, off by default with an environment-variable override, checked before the pickle codec decodes, with an error that names the setting. Happy to use whatever name you prefer.
feat: require opt-in to read data encoded with the pickle codec
feat: require opt-in to read data encoded with the pickle codec (zarr…
docs: add zarr-developers#4465 to the 3.4.2 release notes
docs: 3.4.2 release notes (#4565)