# CVE-2025-1953: vLLM AIBrix Prefix Caching hash.go random values

> Insufficiently random values in prefix caching allow attackers to potentially bypass security mechanisms or predict cache states in vLLM AIBrix.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-2r4h-4cvr-v48c

## What is CVE-2025-1953?

CVE-2025-1953 is a low-severity vulnerability in vLLM AIBrix, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in vLLM AIBrix 0.2.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file pkg/plugins/gateway/prefixcacheindexer/hash.go of the component Prefix Caching. The manipulation leads to insufficiently random values. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 0.3.0 is able to address this issue. It is recommended to upgrade the affected component.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-310

## Which versions are affected by CVE-2025-1953?


## How do I fix CVE-2025-1953?

No fix has been published for CVE-2025-1953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1953 being exploited?

There is no known exploitation of CVE-2025-1953 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1953 and fix it if it is affected.

What it is: CVE-2025-1953 is a low-severity vulnerability in vLLM AIBrix, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1953 in the wild and no public exploit code.

Affected product: vLLM AIBrix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1953/ (Markdown: https://insights.sbomify.com/CVE-2025-1953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1953
- OSV: https://osv.dev/vulnerability/CVE-2025-1953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1953/
Summaries are generated and may contain mistakes; the official description above is the record.