Answer in brief
CVE-2026-90553 records a Unknown severity vulnerability in vLLM before 0.28.0 Remote Code Execution via LlavaOnevision2 processor. The current sources do not mark it as known exploited. The current feed maps vllm-project/vLLM (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps vllm-project/vLLM (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vllm-project/vLLMgeneric | >=0 <0.28.0 | 0.28.0 |
Published upstream
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 12, 2026
vLLM before 0.28.0 contains a remote code execution vulnerability in the LlavaOnevision2 processor loader that ignores the trust_remote_code parameter when loading remote processor classes. Attackers can craft a malicious model with arbitrary code in processing_llava_onevision2.py that executes with vLLM process authority even when trust_remote_code is set to False.
Quoted source text, attributed separately from HOL analysis.