<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: varnish enterprise</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2026-40395: Varnish Enterprise before 6.0.16r12 allows a &quot;workspace overflow&quot; denial of service (daemon panic) for shared </title><link>https://patchthecve.com/cve/CVE-2026-40395.html</link><guid>https://patchthecve.com/cve/CVE-2026-40395.html</guid><pubDate>Mon, 26 Oct 2026 22:10:00 +0000</pubDate><description>MEDIUM 4.0: Varnish Enterprise before 6.0.16r12 allows a &quot;workspace overflow&quot; denial of service (daemon panic) for shared VCL. The headerplus.write_req0() function from vmod_headerplus updates the underlying req0, which is normally the original read-only request from which req is derived (readable and writable </description></item><item><title>CVE-2026-40394: Varnish Cache 9 before 9.0.1 and Varnish Enterprise before 6.0.16r11 allows a &quot;workspace overflow&quot; denial of s</title><link>https://patchthecve.com/cve/CVE-2026-40394.html</link><guid>https://patchthecve.com/cve/CVE-2026-40394.html</guid><pubDate>Mon, 26 Oct 2026 21:10:00 +0000</pubDate><description>MEDIUM 4.0: Varnish Cache 9 before 9.0.1 and Varnish Enterprise before 6.0.16r11 allows a &quot;workspace overflow&quot; denial of service (daemon panic) for certain amounts of prefetched data. The setup of an HTTP/2 session starts with a speculative HTTP/1 transport, and upon upgrading to h2 the HTTP/1 request is repurp</description></item><item><title>CVE-2026-34475: Varnish Cache before 8.0.1 and Varnish Enterprise before 6.0.16r12, in certain unchecked req.url scenarios, mi</title><link>https://patchthecve.com/cve/CVE-2026-34475.html</link><guid>https://patchthecve.com/cve/CVE-2026-34475.html</guid><pubDate>Mon, 26 Oct 2026 22:10:00 +0000</pubDate><description>MEDIUM 5.4: 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.</description></item></channel></rss>