Register for the AI for Security Summit: Join Figma, Perplexity & Wiz

CVE-2026-93894
Linux Debian vulnerability analysis and mitigation

Overview

CVE-2026-93894 is a workspace buffer overflow vulnerability in the .upper() and .lower() string type methods of VCL (Varnish Configuration Language) in Vinyl Cache and Varnish Cache. It can be exploited remotely to cause a denial of service (DoS) by triggering a child process segfault or assertion failure, after which the process automatically restarts. Affected products include Vinyl Cache before version 9.0.2 and Varnish Cache versions 6.3.0 through 8.0.2 and 9.0.0 through 9.0.3. The vulnerability was published on September 18, 2026, with a patch available the same day. It carries a CVSS v4.0 base score of 2.3 (Low) (GitHub Advisory).

Technical details

The root cause is an out-of-bounds write (CWE-787) — also estimated as a classic buffer overflow (CWE-120) — occurring when the .upper() or .lower() VCL string methods process an input string long enough to overflow the remaining workspace buffer at the call site. An attacker must craft an HTTP request containing a sufficiently long string value that fills the workspace without exceeding configured request size limits such as http_req_size and http_req_hdr_len. Exploitation requires prior knowledge of the target's VCL configuration to identify a suitable call site and craft an appropriately sized payload, making the attack complexity high and requiring specific attack preconditions to be present (GitHub Advisory).

Impact

Successful exploitation results in a temporary denial of service: the Vinyl Cache or Varnish Cache child process segfaults or triggers an assertion failure and then automatically restarts, causing brief service unavailability. There is no impact on confidentiality or integrity — the vulnerability is limited to availability of the vulnerable system. Because the child process restarts automatically, the disruption is transient rather than persistent, limiting the overall severity (GitHub Advisory).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the disclosure date (GitHub Advisory). The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is further constrained by the requirement for attacker knowledge of the target VCL configuration and the need to craft requests that stay within configured size limits.

Exploitation steps

  1. Reconnaissance: Identify a target running Vinyl Cache (before 9.0.2) or Varnish Cache (6.3.0–8.0.2 or 9.0.0–9.0.3) exposed over the network.
  2. VCL analysis: Obtain or infer knowledge of the target's VCL configuration to identify locations where .upper() or .lower() string methods are called on attacker-controlled input (e.g., request headers or URL components).
  3. Payload sizing: Determine the approximate remaining workspace size at the vulnerable call site and craft a string payload long enough to overflow it, while keeping the overall request within the server's configured limits (http_req_size, http_req_hdr_len, etc.).
  4. Send crafted request: Transmit an HTTP request containing the oversized string in the appropriate field (e.g., a header value processed by .upper() or .lower() in VCL) to the target server.
  5. Trigger DoS: The buffer overflow causes the child process to segfault or assert, resulting in a process restart and temporary service unavailability (GitHub Advisory).

Indicators of compromise

  • Logs: Repeated child process crash/restart entries in Varnish or Vinyl Cache logs (e.g., Child (PID) died or assertion failure messages); unusual segfault entries in system logs (/var/log/syslog or journalctl).
  • Process: Unexpected restarts of the Varnish/Vinyl Cache child process (varnishd worker) in a short time window.
  • Network: HTTP requests containing unusually long header values or URL components targeting endpoints where VCL applies .upper() or .lower() transformations, particularly requests approaching but not exceeding http_req_size or http_req_hdr_len limits.

Mitigation and workarounds

Upgrade Vinyl Cache to version 9.0.2 or later (git commit 90f5bacc14b2404e6cc349ba015f0f73b8515136 or newer), and upgrade Varnish Cache to version 9.0.4 or later (git commit c5078ae575201b05ae8674a90ddb19ffe7f4b439 or newer) for the 9.x branch; versions 6.3.0–8.0.2 should also be patched per vendor guidance (GitHub Advisory). As a workaround, tighten request size limits (http_req_size, http_req_hdr_len) to reduce the ability to craft payloads large enough to trigger the overflow. Monitor for unexpected child process crashes or restarts as an indicator of exploitation attempts.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Affected

bookworm

varnish

Affected

sid

vinyl-cache

Affected

trixie

varnish

Affected

SourceThis report was generated using AI

Related Linux Debian vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-93574MEDIUM6.5
  • Linux Debian logoLinux Debian
  • netty
NoNoSep 18, 2026
CVE-2026-93562MEDIUM6.5
  • Linux Debian logoLinux Debian
  • netty
NoNoSep 18, 2026
CVE-2026-93894LOW2.3
  • Linux Debian logoLinux Debian
  • varnish
NoNoSep 18, 2026
CVE-2026-82560NONEN/A
  • Linux Debian logoLinux Debian
  • perl
NoNoSep 19, 2026
CVE-2026-78030NONEN/A
  • Linux Debian logoLinux Debian
  • perl-DBI
NoYesSep 19, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management