CVE-2025-48942VulnerabilityPublished 30 May 2025

CVE-2025-48942: vllm · Uncaught Exception

Affects vllmSource CVE Database V5

Mentioned vulnerabilities

CVE-2025-48943

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.9.0 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.9.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vllm-project/vllm to 0.9.0.

Affected software

Product	Affected	Fixed in
GitHubvllm-project/vllm`pkg:github/vllm-project/vllm`Other threats	Affected <0.9.0 >=0.8.0	Fixed in 0.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should upgrade vLLM to version 0.9.0 or later, where this vulnerability is fixed. Until upgrading is possible, organizations can implement strict input validation and filtering at the API gateway or web application firewall (WAF) level to detect and block malformed JSON schema inputs targeting the /v1/completions endpoint. Rate limiting and anomaly detection on API requests can help identify and mitigate potential exploitation attempts. Monitoring server logs for repeated crashes or malformed requests can provide early warning signs. Restricting access to the API endpoint to trusted networks or authenticated users can reduce exposure. Additionally, organizations should conduct regular vulnerability scans and penetration tests focusing on AI inference services to detect similar issues proactively. Maintaining an incident response plan for service outages related to AI inference engines is also advisable.

Description

vLLM is an inference and serving engine for large language models (LLMs). In versions 0.8.0 up to but excluding 0.9.0, hitting the /v1/completions API with a invalid json_schema as a Guided Param kills the vllm server. This vulnerability is similar GHSA-9hcf-v7m4-6m2j/CVE-2025-48943, but for regex instead of a JSON schema. Version 0.9.0 fixes the issue.

Impact

For European organizations deploying vLLM versions 0.8.0 to before 0.9.0, this vulnerability poses a risk primarily to service availability. Organizations using vLLM to serve AI or language model inference could experience denial of service if attackers send malformed requests to the /v1/completions API, causing server crashes. This could disrupt AI-driven applications, customer-facing chatbots, or internal automation relying on LLM inference, potentially impacting business operations and user experience. Given the growing adoption of AI technologies in sectors such as finance, healthcare, and public services across Europe, service interruptions could have operational and reputational consequences. However, since the vulnerability does not allow data breach or code execution, the confidentiality and integrity of data remain unaffected. The requirement for low privileges but no user interaction means internal threat actors or attackers with some access to the API endpoint could exploit this. The absence of known exploits in the wild reduces immediate risk but patching is recommended to prevent future exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 13:56 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats