Advisory record · GHSA-3c86-2m5g-59q7

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. Attacke...

CVSS 8.5 HighEPSS 0.0031 · 23rd percentile

Published by the maintainers · not yet reviewed by GitHub. The vllm-project/vllm maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the vllm-project/vllm maintainers at 12 Sept 2026, 13:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
vllmPyPI<0.28.00.28.0
Identifiers
GHSA-3c86-2m5g-59q7 · CVE-2026-90553 · PYSEC-2026-3985
Weakness (CWE)
CWE-94
Published
12 Sept 2026
Updated
17 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

vLLM versions before 0.28.0 are vulnerable to remote code execution in the LlavaOnevision2 processor loader, which loads remote processor classes without honoring the trust_remote_code setting. An attacker who can supply a malicious model can run arbitrary code with the privileges of the vLLM process, even when trust_remote_code is False. Upgrade to vLLM 0.28.0 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.5 High 4.0 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 23rd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 28 Aug 2026, 18:05 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:10 UTC First seen by agentprime
  3. 31 Oct 2026, 14:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.