CVE-2026-40395: High severity Varnish Software Varnish Enterprise vulnerability
Varnish Enterprise before 6.0.16r12 allows a "workspace overflow" denial of service (daemon panic) for shared VCL. The headerplus.writereq0() function from vmodheaderplus updates the underlying req0, which is normally the original read-only request from which req is derived (readable and writable from VCL). This is useful in the active VCL, after amending req, to prepare a refined req0 before switching to a different VCL with the return (vcl(<label>)) action. This is for example how the Varnish Controller operates shared VCL deployments. If the amended req contained too many header fields for req0, this would have resulted in a workspace overflow that would in turn trigger a panic and crash the Varnish Enterprise server. This could be used as a Denial of Service attack vector by malicious clients.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40395?
CVE-2026-40395 is classified as a denial of service vulnerability that can lead to a daemon panic.
How do I fix CVE-2026-40395?
To mitigate CVE-2026-40395, users should upgrade to Varnish Enterprise version 6.0.16r12 or later.
What versions of Varnish Enterprise are affected by CVE-2026-40395?
CVE-2026-40395 affects Varnish Enterprise versions earlier than 6.0.16r12.
What type of issue does CVE-2026-40395 represent?
CVE-2026-40395 represents a workspace overflow issue that results in a denial of service.
Can CVE-2026-40395 be exploited by remote attackers?
Yes, CVE-2026-40395 can be exploited by remote attackers to cause a service disruption.