# CVE-2025-11915: HTTP Desynchronisation in Vertex AI for certain third-party models

> HTTP desynchronization in Vertex AI proxies could allow request smuggling, but Google has already patched all affected proxies.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:L/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 23 Oct 2025
- **Also known as:** GHSA-cwmv-37m7-7829

## What is CVE-2025-11915?

CVE-2025-11915 is a medium-severity vulnerability in Google Cloud Vertex AI: Open Models for MaaS, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Connection desynchronization between an HTTP proxy and the model backend. The fixes were rolled out for all proxies in front of impacted models by 2025-09-28. Users do not need to take any action.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

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

## Is CVE-2025-11915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11915 is a medium-severity vulnerability in Google Cloud Vertex AI: Open Models for MaaS, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11915 in the wild and no public exploit code.

Affected product: Google Cloud Vertex AI: Open Models for MaaS. 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-11915/ (Markdown: https://insights.sbomify.com/CVE-2025-11915/index.md)
```

## Sources

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

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