Remote code execution via hardcoded trust override
Published Mar 26, 2026 · Updated Mar 26, 2026
Protection mechanism failure in vLLM 0.10.1 and later before 0.18.0 allows remote attackers to execute Python code from malicious model repositories. NemotronVL passes a hardcoded true trust setting to AutoModel.from_config, while KimiK25 does the same in cached_get_image_processor, ignoring the global false setting. Exploitation requires an operator to load an attacker-controlled repository for either affected model; code then runs with the serving process's privileges.
Summary
What happened
Protection mechanism failure in vLLM 0.10.1 and later before 0.18.0 allows remote attackers to execute Python code from malicious model repositories. NemotronVL passes a hardcoded true trust setting to AutoModel.from_config, while KimiK25 does the same in cached_get_image_processor, ignoring the global false setting. Exploitation requires an operator to load an attacker-controlled repository for either affected model; code then runs with the serving process's privileges.
The record
- CVE
- CVE-2026-27893
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- vLLM Project
- Product
- vLLM
- Classifications
- CWE-501, CWE-693, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.10.1, < 0.18.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo