Skip to content

Investigate Accelerate checkpoint path traversal - #24

Merged
Happy (huangyangyu) merged 1 commit into
mainfrom
copilot/fix-accelerate-vulnerability
Nov 17, 2026
Merged

Happy (huangyangyu) merged 1 commit into
mainfrom
copilot/fix-accelerate-vulnerability

Conversation

@huangyangyu

@huangyangyu Happy (huangyangyu) commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Accelerate accepts unsanitized shard paths from checkpoint indexes, allowing path traversal or denial of service. The repository pins an affected version.

  • Status: No dependency change is proposed. The advisory lists no patched version or workaround; versions 1.15.0 and 1.16.0 still contain the vulnerable path handling.
  • Reachability assessment — medium confidence: The direct load_checkpoint_and_dispatch call passes a .bin file, not a sharded index. Indirect reachability through Transformers remains uncertain.
  • Next step: Await a verified upstream fix and review the dependency upgrade.
Original prompt

This section details the Dependabot vulnerability alert you should resolve

<alert_title>Accelerate path traversal and denial of service via sharded checkpoint weight_map entries</alert_title>
<alert_description>Hugging Face Accelerate through 1.14.0 contains a path traversal vulnerability in load_checkpoint_in_model and load_checkpoint_and_dispatch functions that fail to sanitize weight_map entries from sharded checkpoint indexes. Attackers can supply relative paths with ../ sequences or absolute paths to read arbitrary files, or point shard entries at named pipes to cause indefinite blocking and denial of service.</alert_description>

moderate
GHSA-4j2p-28q2-5m79, CVE-2026-69112
accelerate
pip
<vulnerable_versions>= 1.7.0</vulnerable_versions>
<patched_version></patched_version>
<manifest_path>requirements.txt</manifest_path>

https://nvd.nist.gov/vuln/detail/CVE-2026-69112 https://github.com/huggingface/accelerate/issues/4067 https://github.com/huggingface/accelerate/pull/4070 https://github.com/huggingface/accelerate/pull/4138 https://www.vulncheck.com/advisories/hugging-face-accelerate-path-traversal-and-dos-via-weight-map https://github.com/advisories/GHSA-4j2p-28q2-5m79

<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking changes that are found. If the package manager fails to resolve dependencies (e.g. peer dependency conflicts, incompatible engine constraints), document the error in the PR description rather than attempting increasingly complex workarounds. After updating, check the lock file to confirm the package no longer resolves to a version in the vulnerable range. Keep changes minimal and tightly scoped. Ensure tests, build, type checking, and linting all pass after your changes. If there are any test, lint, or typechecking failures, investigate whether they are caused by the update and fix them if so — do not leave broken tests in the PR. If they were already present before the update, note them in the PR description so a human reviewer can assess whether they are related.</task_instructions>

  • Resolves microsoft/data-efficacy alert #97

@huangyangyu Happy (huangyangyu) changed the title [WIP] Fix path traversal vulnerability in Hugging Face Accelerate Investigate Accelerate checkpoint path traversal Nov 17, 2026
@huangyangyu
Happy (huangyangyu) marked this pull request as ready for review November 17, 2026 07:10
@huangyangyu
Happy (huangyangyu) merged commit dc13918 into main Nov 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants