CVE-2025-61620

[vllm] Resource-Exhaustion (DoS) through chat_template / chat_template_kwargs in OpenAI-Compatible Server

Verified by Precogs Threat Research
Last Updated: Oct 7, 2025
Base Score
5.5MEDIUM

Executive Summary

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

Precogs AI Insight

"Precogs AI automatically detects AI-specific vulnerability patterns in LLM-generated code, identifying prompt injection vectors, model poisoning risks, and insecure inference endpoints before they reach production."

Exploit Probability
Low (<10%)
Public POC
Undisclosed
Exploit Probability
Low (<10%)
Public POC
Available
Affected Assets
ai codeappsecvllmCWE-20

What is this vulnerability?

CVE-2025-61620 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 resource-exhaustion (denial-of-service) vulnerability exists in multiple endpoints of the OpenAI-Compatible Server due to the ability to s.

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 Score5.5 (MEDIUM)
Vector StringN/A
PublishedOctober 7, 2025
Last ModifiedOctober 7, 2025
Related CWEsCWE-20, CWE-400, CWE-770, CWE-789

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

Related Vulnerabilitiesvia CWE-20