# CVE-2025-30346: Other in Varnish Cache

> Attackers can exploit HTTP/1 request desync in Varnish Cache to bypass security controls or poison caches.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2025
- **Updated:** 3 Apr 2025
- **Also known as:** ALPINE-CVE-2025-30346, BIT-varnish-2025-30346, DEBIAN-CVE-2025-30346, DLA-4101-1, GHSA-hxcm-q7m2-7qhp, OESA-2025-1333, UBUNTU-CVE-2025-30346, openSUSE-SU-2025:14992-1

## What is CVE-2025-30346?

CVE-2025-30346 is a medium-severity vulnerability in varnish-software Varnish Cache, published on 21 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Varnish Cache before 7.6.2 and Varnish Enterprise before 6.0.13r10 allow client-side desync via HTTP/1 requests.

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

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

1 open source package ship an affected version, including varnish. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `varnish` | Bitnami | All versions | None |
| `varnish` | openSUSE:Tumbleweed | All versions | 7.7.0-1.1 |

Products: Varnish-Software Varnish Enterprise, Varnish Cache Project Varnish Cache.

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

Upgrade to a fixed version.

## Is CVE-2025-30346 being exploited?

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

## Other vulnerabilities in varnish-software Varnish Cache

- [CVE-2023-41104](https://insights.sbomify.com/CVE-2023-41104/): Memory corruption in n/a (medium 6.5)
- [CVE-2026-34475](https://insights.sbomify.com/CVE-2026-34475/): Varnish Cache before 8.0.1 and Varnish Enterprise before 6.0.16r12, in certain unchecked req.url scenarios, mishandle URLs with a path of / (medium 5.4)
- [CVE-2026-40394](https://insights.sbomify.com/CVE-2026-40394/): Denial of service in Varnish Cache (medium 4.0)
- [CVE-2026-40395](https://insights.sbomify.com/CVE-2026-40395/): Denial of service in Varnish Enterprise (medium 4.0)
- [CVE-2025-30347](https://insights.sbomify.com/CVE-2025-30347/): Information disclosure in Varnish Enterprise (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30346 is a medium-severity vulnerability in varnish-software Varnish Cache, published on 21 Mar 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-30346 in the wild and no public exploit code.

Affected packages and fixed versions:
- varnish (Bitnami): affected all versions; no fix listed

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-30346/ (Markdown: https://insights.sbomify.com/CVE-2025-30346/index.md)
```

## Sources

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

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