vllm: Insertion of Sensitive Information into Log File
CVE-2026-22778 is a critical-severity insertion of sensitive information into log file vulnerability in vllm from Vllm-project, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected vllm versions: >= 0.8.3, < 0.14.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 18.3% chance of exploitation within 30 days, which is in the top 2.73% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of vllm you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Vllm-project | vllm | >= 0.8.3, < 0.14.1 | Not stated |
| Red Hat | Red Hat AI Inference Server 3.2 | Not specified in the record | Not stated |
| Red Hat | Red Hat AI Inference Server 3.3 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI 2.25 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI 3.3 | Not specified in the record | Not stated |
| Red Hat | Red Hat AI Inference Server | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux AI (RHEL AI) 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI (RHOAI) | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (github.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (github.com) |
| CVSS 3.1 | 9.8 | Critical | CNA |
Official description
vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid image is sent to vLLM's multimodal endpoint, PIL throws an error. vLLM returns this error to the client, leaking a heap address. With this leak, we reduce ASLR from 4 billion guesses to ~8 guesses. This vulnerability can be chained a heap overflow with JPEG2000 decoder in OpenCV/FFmpeg to achieve remote code execution. This vulnerability is fixed in 0.14.1.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How developers prevent this class of flaw
- Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Remove debug log files before deploying the application into production.
- Protect log files against unauthorized read/write.
More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/vllm-project/vllm/pull/31987Issue Tracking
- github.com/vllm-project/vllm/pull/32319Issue Tracking
- github.com/vllm-project/vllm/releases/tag/v0.14.1Release Notes
Other references
- access.redhat.com/errata/RHSA-2026:19712
- access.redhat.com/errata/RHSA-2026:30087
- access.redhat.com/errata/RHSA-2026:30088
- access.redhat.com/errata/RHSA-2026:30089
- access.redhat.com/errata/RHSA-2026:3461
- access.redhat.com/errata/RHSA-2026:3462
- access.redhat.com/errata/RHSA-2026:3713
- access.redhat.com/errata/RHSA-2026:3782
- access.redhat.com/security/cve/CVE-2026-22778
- bugzilla.redhat.com/show_bug.cgi?id=2436113
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-22778.json
Other vulnerabilities in vllm
- 7.5 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.7 High severity
- 7.5 High severity
- 7.5 High severity
Recent Insertion of Sensitive Information into Log File vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.