Threats Tagged 'cve-2026-100653'
View all threats tagged with 'cve-2026-100653'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-100653'
Click on any threat for detailed analysis and mitigation recommendations
vLLM versions 0.22.1 through 0.28.0 have a vulnerability where the operator-supplied model revision pin (--revision / --code-revision) is not correctly propagated to certain Hugging Face artifact loads for FunAudioChat and Tarsier2 architectures. This causes deployments pinned to a specific revision to still fetch some processor, tokenizer, and configuration artifacts from the repository's default revision, potentially altering behavior without operator intent. This issue affects supply-chain integrity and reproducibility but does not allow remote code execution or bypass trust_remote_code settings. The vulnerability is fixed in version 0.28.0. Join the discussion | GCVE Database | 09/26/2026, 15:31:18 UTC Added: 09/27/2026, 04:30:24 UTC |
0 vLLM is an inference and serving engine for large language models. In versions from 0.22.1 through 0.28.0, the operator-supplied model revision pin (--revision / --code-revision) is not propagated to several Hugging Face artifact loads for the FunAudioChat and Tarsier2 architectures: the WhisperFeatureExtractor and speech_tokenizer PreTrainedTokenizerFast loads in vllm/model_executor/models/funaudiochat.py and the Qwen2VLConfig.from_pretrained call used by Tarsier2ProcessingInfo in vllm/model_executor/models/qwen2_vl.py. As a result, deployments pinned to a reviewed revision still resolve these behavior-affecting processor, tokenizer, and config artifacts from the repository's default revision, so a later change to the upstream default branch can alter audio preprocessing, speech tokenizer behavior, or Tarsier2 configuration without any change to the operator's configured pin. This is a supply-chain integrity and reproducibility failure for pinned deployments; it is residual to the earlier fix tracked as GHSA-3ww4-5jv9-j5gm / CVE-2026-47155 and does not constitute remote code execution or a trust_remote_code=False bypass. The issue is fixed in version 0.28.0. Join the discussion | CVE Database V5 | 09/26/2026, 13:23:22 UTC Added: 09/26/2026, 13:33:29 UTC |
Showing 1 to 2 of 2 results