CVE-2026-40396: High severity Varnish Software Varnish Cache vulnerability
Varnish Cache 9 before 9.0.1 allows a "workspace overflow" denial of service (daemon panic) after timeoutlinger. A malicious client could send an HTTP/1 request, wait long enough until the session releases its worker thread (timeoutlinger) and resume traffic before the session is closed (timeoutidle) sending more than one request at once to trigger a pipelining operation between requests. This vulnerability affecting Varnish Cache 9.0.0 emerged from a port of the Varnish Enterprise non-blocking architecture for HTTP/2. New code was needed to adapt to a more recent workspace API that formalizes the pipelining operation. In addition to the workspace change on the Varnish Cache side, other differences created merge conflicts, like partial support for trailers in Varnish Enterprise. The conflict resolution missed one code path configuring pipelining to perform a complete workspace rollback, losing the guarantee that prefetched data would fit inside workspaceclient during the transition from one request to the next. This can result in a workspace overflow, triggering a panic and crashing the Varnish server.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40396?
CVE-2026-40396 has a severity rating that indicates it can lead to denial of service through daemon panic.
How do I fix CVE-2026-40396?
To fix CVE-2026-40396, upgrade Varnish Cache to version 9.0.1 or later.
What type of vulnerability is CVE-2026-40396?
CVE-2026-40396 is classified as a denial of service vulnerability.
Which versions of Varnish Cache are affected by CVE-2026-40396?
CVE-2026-40396 affects Varnish Cache versions prior to 9.0.1.
What causes the denial of service in CVE-2026-40396?
The denial of service in CVE-2026-40396 is caused by a workspace overflow related to the timeout_linger parameter.