vllm - 💡(How to fix) Fix releases/v0.10.1: CVE-2026-22807 trust_remote_code gate missing in transformers backend [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#41143Fetched 2026-04-29 06:12:07
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
added_to_project_v2 ×1project_v2_item_status_changed ×1
RAW_BUFFERClick to expand / collapse

vllm/transformers_utils/dynamic_module.py:13 defines try_get_class_from_dynamic_module() without a trust_remote_code parameter on releases/v0.10.1 (sha not yet bumped to 78d13ea9). The upstream CVE-2026-22807 fix 78d13ea9 — "[Model] Handle trust_remote_code for transformers backend (#32194)" — adds an explicit resolve_trust_remote_code(...) gate before get_class_from_dynamic_module(...) so that loading a custom HuggingFace *.py is no longer accepted unconditionally; it also threads model_config.trust_remote_code through both call sites in _try_resolve_transformers (vllm/model_executor/models/registry.py:887 and :899). Both call sites still pass without the kwarg on this branch, and the resolve_trust_remote_code import is missing in the dynamic-module helper. If releases/v0.10.1 is still on the security-fix list I am happy to send a clean cherry-pick.

extent analysis

TL;DR

Apply the security fix from commit 78d13ea9 to address the CVE-2026-22807 vulnerability by adding the trust_remote_code parameter and resolve_trust_remote_code gate.

Guidance

  • Review the changes in commit 78d13ea9 to understand the security fix and its implications.
  • Cherry-pick the commit to the releases/v0.10.1 branch to apply the fix.
  • Verify that the resolve_trust_remote_code function is properly imported and used in the dynamic_module.py file.
  • Test the updated code to ensure that the trust_remote_code parameter is correctly passed to the try_get_class_from_dynamic_module function.

Example

No code snippet is provided as the issue does not require a new code example, but rather applying an existing security fix.

Notes

The provided guidance assumes that the releases/v0.10.1 branch is still being maintained and that the security fix is applicable to this version.

Recommendation

Apply the workaround by cherry-picking the commit 78d13ea9 to the releases/v0.10.1 branch, as this will address the CVE-2026-22807 vulnerability and add the necessary trust_remote_code parameter and resolve_trust_remote_code gate.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix releases/v0.10.1: CVE-2026-22807 trust_remote_code gate missing in transformers backend [1 participants]