On this page (7 sections)

Debian published DSA-6584-1 on October 25, 2026, a security update for the varnish package. It covers two vulnerabilities in Varnish Cache, the HTTP accelerator many sites place in front of their web servers: one that can lead to cache poisoning or authentication bypass, and one that can crash the worker process.

If you run Varnish, Vinyl Cache or Varnish Enterprise in front of an application, especially on Debian, this is worth a quick version check. Neither issue is reported as exploited in the sources reviewed, and both depend on how your configuration is written.

What Debian fixed

The Debian advisory bundles two separate flaws. The first, CVE-2026-34475, was reported by Tom Kinnaird of Claranet Limited according to the Varnish vendor advisory VSV00018. The second, CVE-2026-93894, was credited by Debian to Tristan Madani. Debian's fixed version applies to the stable release, trixie.

Technical details

CVE-2026-34475: absolute-form URL parsing

HTTP/1.1 allows a request target in "absolute form", where the full URL (scheme and host) appears in the request line instead of only the path. The vendor describes a deficiency in how Varnish parses these requests. If the req.url VCL variable is passed unchecked to a backend that accepts absolute-form URIs, the result can be cache poisoning or authentication bypass.

The attack surface is narrow. According to the vendor, it is limited to root URLs with a path of /, such as https://example.com/, and does not extend to paths like /whatever. The weakness is classified as CWE-180, validating input before it is canonicalized. In plain terms, one part of the stack checks the URL in one form while another interprets it in a different form, and the gap can be abused. The GitHub advisory lists the CVSS v3.1 vector as network-reachable, high complexity, no privileges and no user interaction.

CVE-2026-93894: VCL case-conversion overflow

This is a workspace buffer overflow in the .upper() and .lower() string methods of VCL, the Varnish Configuration Language. A remote request could make the child process segfault or assert and then restart, which is a denial of service. The GitHub advisory notes that exploiting it effectively requires prior knowledge of the VCL in use and a request with a string long enough to fill the remaining workspace while staying under request size limits such as http_req_size and http_req_hdr_len. Debian adds that it depends on the configuration applying these methods to attacker-controlled strings.

The CVE description for CVE-2026-93894 says "Vinyl Cache before 9.0,2", which looks like a typographical error. The sources reviewed do not give a clear upstream fixed version for this CVE, only Debian's package version, so check the vendor advisory VSV00020 for the exact fixed release.

Who is realistically exposed

  • Debian trixie hosts running the varnish package: update to 7.7.0-3+deb13u2.
  • Operators of upstream Varnish Cache 8.0.0 or earlier, or the 6.0 LTS series up to 6.0.16, for CVE-2026-34475.
  • Varnish Enterprise 6.0.x users up to 6.0.16r11.
  • Sites whose VCL passes req.url unchanged to a backend that accepts absolute-form URIs. Backends that reject such requests reduce the risk for CVE-2026-34475.
  • Sites whose VCL calls .upper() or .lower() on request-derived strings, for CVE-2026-93894. The severity is low, but a crash and restart empties the cache and can cause a load spike on the origin.

Sites that do not run Varnish are not affected. Managed hosting customers may not control this layer, so ask the provider whether it uses Varnish and when it applied the fix.

How to check your exposure

On Debian, this command shows the installed and candidate varnish package versions. Compare the installed version with 7.7.0-3+deb13u2 on trixie.

Show installed and candidate varnish package version (Debian)Shell
apt policy varnish

On any platform, this asks the installed binary for its version. Compare it with the affected ranges above.

Print the Varnish version (any Linux host with varnishd installed)Shell
varnishd -V

Then review your VCL for two things: whether req.url is passed to a backend without validation, and whether .upper() or .lower() is used on strings from the request. This search lists VCL lines that call these methods; any match deserves a look at what string it operates on.

Search VCL files for case-conversion calls (default config directory; adjust the path if yours…Shell
grep -rnE '\.(upper|lower)\(' /etc/varnish/

What to do now

  1. Identify every host running Varnish, Vinyl Cache or Varnish Enterprise, including containers and managed services.
  2. On Debian trixie, update the varnish package to 7.7.0-3+deb13u2 or later.
  3. On other platforms, upgrade to Varnish Cache 8.0.1, 6.0.17, Varnish Enterprise 6.0.16r12 or later, or Vinyl Cache 9.0.
  4. If you cannot upgrade yet, add the vendor's VCL mitigation for CVE-2026-34475 (below).
  5. Check your backend's handling of absolute-form request URIs and reject them if your application does not need them.
  6. Review VCL for .upper() and .lower() on request data and confirm request size limits are set sensibly.
  7. Confirm the fix by rechecking the version and watching the cache after restart.

To update on Debian, run the following as root or with sudo. It upgrades only the varnish package and then restarts the service so the new version is running.

Caution. Restarting Varnish empties the in-memory cache and can briefly raise load on your origin server. Do this during a quiet period and expect slower responses while the cache refills.
Upgrade the varnish package and restart the service (Debian)Shell
sudo apt update && sudo apt install --only-upgrade varnish
sudo systemctl restart varnish

If upgrading is not possible, the vendor's advisory provides this VCL snippet to add at the top of your VCL. It returns a 400 for request URLs that do not begin with a slash, while still allowing OPTIONS * and CONNECT requests. The vendor notes it was also added to the built-in VCL as a precaution. Test it on a staging instance first.

Vendor mitigation for CVE-2026-34475 (from VSV00018), place at top of your VCLText
sub vsv18 {
  if (req.url == "*" && req.method == "OPTIONS") {
    return;
  }
  # NB: we do not allow connect by default (see vcl_req_method)
  if (req.url !~ "^/" && req.method != "CONNECT") {
    return (synth(400));
  }
}
sub vcl_recv {
  call vsv18;
}
Tip. Whatever your VCL does, keep your origin from trusting the cache layer for authentication decisions. Enforce access control in the application itself so a cache quirk cannot grant access.

Detection and monitoring afterwards

The sources do not describe indicators of compromise, so treat the following as general hygiene. Look in your access logs for requests where the request target starts with http:// or https:// rather than a path, since browsers normally send only the path to a web server. Watch for unexpected content served on your home page, which is the root URL the flaw concerns, and for repeated Varnish child restarts in the system journal, which could point to the crash behavior of CVE-2026-93894 or to unrelated problems.

A quick outside check of your home page headers can reveal unexpected changes. The free security headers checker shows what your site returns, and Webforta Monitor can alert you to header and certificate changes over time. For background on how reverse proxies and filters fit together, see What is a WAF?.

Timeline

Key dates from the vendor, GitHub and Debian advisories
DateEvent
2026-03-16Varnish advisory VSV00018 dated; Varnish Cache 8.0.1, 6.0.17 and Vinyl Cache 9.0 released
2026-03-27CVE-2026-34475 published to the GitHub Advisory Database
2026-09-18CVE-2026-93894 published to the GitHub Advisory Database
2026-10-25Debian publishes DSA-6584-1 with fixed version 7.7.0-3+deb13u2 for trixie

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-34475 - GitHub Advisory Databasegithub.com
  2. VSV00018 Varnish Cache absolute form parsing deficiency - Vinyl Cachevinyl-cache.org
  3. CVE-2026-93894 - GitHub Advisory Databasegithub.com
  4. [SECURITY] [DSA 6584-1] varnish security updatelists.debian.org ·
  • Varnish
  • Debian
  • Cache poisoning
  • Reverse proxy
  • Patch management