GPU VulnDB

Database/AI/ML frameworks & serving

Hugging Face Accelerate: unsanitized shard paths in a checkpoint index give arbitrary file read and hangs

CVSS 6.9CVE-2026-69112AI/ML frameworks & servingcurated

Impact

Accelerate through 1.14.0 trusts the weight_map entries inside a sharded checkpoint index, so a checkpoint whose index points at ../../etc/... or an absolute path makes the loading process open and read that file instead of a shard. A shard entry pointing at a named pipe blocks the loader indefinitely, stalling the job and holding its GPUs. Any pipeline that loads third-party or user-supplied checkpoints - a model hub mirror, a customer-uploaded fine-tune, a shared scratch filesystem - is the delivery path. The read runs with the privileges of the training or serving process, which on a GPU node often means access to tokens and mounted credentials.

Who can reach it

Anyone who can place or supply a checkpoint directory that the fleet loads; no authentication to the loader itself, but it requires the victim process to load the attacker's checkpoint.

What to do

Upgrade accelerate past 1.14.0 to a release containing the sanitization fix (PRs 4070 and 4138) - no fixed version is stated in the record - rebuild the images that pin it, and restart training and serving jobs. Interim mitigation: only load checkpoints from trusted stores, and validate that every weight_map path is relative and stays inside the checkpoint directory before loading.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.