CVE-2025-62164

[vllm] prompt_embeds deserialization allows DoS and potential RCE

Verified by Precogs Threat Research
Last Updated: Jan 8, 2026
Base Score
8HIGH

Executive Summary

CVE-2025-62164 is a high severity vulnerability affecting appsec, binary-analysis, ai-code. It is classified as CWE-20. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"The fundamental weakness here is traced back to within ### Summary, allowing a lack of rigorous type checking mechanisms. Adversaries commonly weaponize this defect by execute arbitrary code on the target system, potentially leading to full system compromise. By intercepting insecure data flows from user input directly to rendering sinks, Precogs is designed to prevent unauthorized logical exploitation."

Exploit Probability (EPSS)
Low (0.2%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecbinary analysisai codeCWE-20

What is this vulnerability?

CVE-2025-62164 is categorized as a critical Improper Input Validation flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Summary A memory corruption vulnerability that leading to a crash (denial-of-service) and potentially remote code execution (RCE) exists in vLLM versi.

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score8 (HIGH)
Vector StringN/A
PublishedNovember 20, 2025
Last ModifiedJanuary 8, 2026
Related CWEsCWE-20, CWE-123, CWE-502, CWE-787

Impact on Systems

Chained Exploitation: Serves as the root cause enabling XSS, SQLi, and Command Injection attacks down the execution chain.

Business Logic Bypass: Manipulating unexpected inputs (e.g., negative integers for price amounts) subverts core business logic.

Denial of Service: Sending massively oversized or recursively complex inputs can exhaust CPU/Memory parsing limits.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Strict Allow-listing Define rigid, regex-based allow-lists for all input vectors, rejecting any data that does not conform to the expected length, type, and format.

2. Type Juggling Prevention Utilize strong static typing and strictly compare variable types before processing data structures.

3. API Gateway Defenses Deploy Web Application Firewalls (WAF) and central API Gateways to strip malformed payloads before they reach internal services.

Vulnerability Signature

// Improper Validation resulting in unexpected logic execution
function process_order(quantity) \{
    // VULNERABLE: No check if quantity is positive or an integer
    let total_price = quantity * 100.00;
    user_balance -= total_price; // Negative quantity INCREASES balance
\}

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUntrusted User Input
VectorInput flows through the application logic without sanitization
SinkExecution or Rendering Sink
ImpactApplication compromise, Logic Bypass, Data Exfiltration

Vulnerable Code Pattern

# ❌ VULNERABLE: Unsanitized Input Flow
def process_request(request):
    user_input = request.GET.get('data')
    # Taint sink: processing untrusted data
    execute_logic(user_input)
    return {"status": "success"}

Secure Code Pattern

# ✅ SECURE: Input Validation & Sanitization
def process_request(request):
    user_input = request.GET.get('data')
    
    # Sanitized boundary check
    if not is_valid_format(user_input):
        raise ValueError("Invalid input format")
        
    sanitized_data = sanitize(user_input)
    execute_logic(sanitized_data)
    return {"status": "success"}

How Precogs Detects This

Precogs AI Analysis Engine maps untrusted input directly to execution sinks to catch complex application security vulnerabilities.\n

Related Vulnerabilitiesvia CWE-20

CVE-2026-322016.5 MEDIUM

Improper Input Validation in Improper input validation in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing over a network

CWE-20
CVE-2026-341978.8 HIGH

Improper Input Validation in Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ

CWE-20CWE-94
CVE-2026-48600 HIGH

CVE-2026-4860: Unsafe Deserialization in wvp-GB28181-pro

CWE-502CWE-20
CVE-2025-599447.5 HIGH

Cursor Case-Sensitivity File-Handling Flaw in agentic IDE

CWE-20
CVE-2026-36415.3 MEDIUM

The Appmax plugin for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 1.

CWE-20
CVE-2026-34605.3 MEDIUM

The REST API TO MiniProgram plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.

CWE-20

Is your system affected?

Precogs AI detects CVE-2025-62164 in compiled binaries, LLMs, and application layers — even without source code access.