Issue Station
Sign In
Tools hereToolbox

vllm - 💡(How to fix) Fix Backport CVE-2026-22807 (transformers-backend trust_remote_code) to releases/v0.10.2? [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#41152•Fetched 2026-04-29 06:12:03
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
vulgraphvulgraph
Participants
vulgraphvulgraph
Timeline (top)
added_to_project_v2 ×1project_v2_item_status_changed ×1

Fix Action

Fix / Workaround

CVE-2026-22807 patch 78d13ea9 doesn't look to be present on releases/v0.10.2:

RAW_BUFFERClick to expand / collapse

CVE-2026-22807 patch 78d13ea9 doesn't look to be present on releases/v0.10.2:

  • vllm/transformers_utils/dynamic_module.py is missing the resolve_trust_remote_code import and the new trust_remote_code parameter on try_get_class_from_dynamic_module().
  • Both call sites in vllm/model_executor/models/registry.py::_try_resolve_transformers (the warn_on_fail=False and warn_on_fail=True arms) still call into the dynamic-module helper without forwarding model_config.trust_remote_code.

Net effect: a transformers-backend model that ships a *.py definition can be loaded via get_class_from_dynamic_module without honoring --trust-remote-code, which is the exact path the CVE writeup flags. Happy to draft a backport PR if releases/v0.10.2 is in the support window.

Cheers, vulgraph

extent analysis

TL;DR

The CVE-2026-22807 patch is missing from the releases/v0.10.2 branch, allowing transformers-backend models to load without honoring the --trust-remote-code flag.

Guidance

  • Verify the presence of the resolve_trust_remote_code import and the trust_remote_code parameter in vllm/transformers_utils/dynamic_module.py to ensure the patch is applied.
  • Check the call sites in vllm/model_executor/models/registry.py::_try_resolve_transformers to confirm that the trust_remote_code parameter is being forwarded to the dynamic-module helper.
  • Consider backporting the patch to the releases/v0.10.2 branch if it is within the support window to mitigate the vulnerability.
  • Review the transformers-backend model loading process to ensure that it honors the --trust-remote-code flag as expected.

Notes

The provided information suggests that the patch for CVE-2026-22807 is missing from the releases/v0.10.2 branch, but it does not provide enough context to determine the full extent of the issue or the best course of action for all possible scenarios.

Recommendation

Apply workaround: Backport the CVE-2026-22807 patch to the releases/v0.10.2 branch if it is within the support window, as this will mitigate the vulnerability and ensure that the --trust-remote-code flag is honored as expected.

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…
#cache error#pipeline error#runtime error#dependency conflict#environment setup

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 Backport CVE-2026-22807 (transformers-backend trust_remote_code) to releases/v0.10.2? [1 participants]