https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2022-45060.htmlhttps://patchthecve.com/cve/CVE-2022-45060.htmlWed, 17 Jun 2026 05:09:16 +0000HIGH 7.5: An HTTP Request Forgery issue was discovered in Varnish Cache 5.x and 6.x before 6.0.11, 7.x before 7.1.2, and 7.2.x before 7.2.1. An attacker may introduce characters through HTTP/2 pseudo-headers that are invalid in the context of an HTTP/1 request line, causing the Varnish server to produce invalhttps://patchthecve.com/cve/CVE-2022-45059.htmlhttps://patchthecve.com/cve/CVE-2022-45059.htmlWed, 17 Jun 2026 05:09:15 +0000HIGH 7.5: An issue was discovered in Varnish Cache 7.x before 7.1.2 and 7.2.x before 7.2.1. A request smuggling attack can be performed on Varnish Cache servers by requesting that certain headers are made hop-by-hop, preventing the Varnish Cache servers from forwarding critical headers to the backend.https://patchthecve.com/cve/CVE-2022-38150.htmlhttps://patchthecve.com/cve/CVE-2022-38150.htmlWed, 17 Jun 2026 04:56:11 +0000HIGH 7.5: In Varnish Cache 7.0.0, 7.0.1, 7.0.2, and 7.1.0, it is possible to cause the Varnish Server to assert and automatically restart through forged HTTP/1 backend responses. An attack uses a crafted reason phrase of the backend response status line. This is fixed in 7.0.3 and 7.1.1.https://patchthecve.com/cve/CVE-2022-23959.htmlhttps://patchthecve.com/cve/CVE-2022-23959.htmlWed, 17 Jun 2026 04:31:03 +0000CRITICAL 9.1: In Varnish Cache before 6.6.2 and 7.x before 7.0.2, Varnish Cache 6.0 LTS before 6.0.10, and and Varnish Enterprise (Cache Plus) 4.1.x before 4.1.11r6 and 6.0.x before 6.0.9r4, request smuggling can occur for HTTP/1 connections.https://patchthecve.com/cve/CVE-2021-36740.htmlhttps://patchthecve.com/cve/CVE-2021-36740.htmlWed, 17 Jun 2026 03:59:05 +0000MEDIUM 6.5: Varnish Cache, with HTTP/2 enabled, allows request smuggling and VCL authorization bypass via a large Content-Length header for a POST request. This affects Varnish Enterprise 6.0.x before 6.0.8r3, and Varnish Cache 5.x and 6.x before 6.5.2, 6.6.x before 6.6.1, and 6.0 LTS before 6.0.8.https://patchthecve.com/cve/CVE-2020-11653.htmlhttps://patchthecve.com/cve/CVE-2020-11653.htmlWed, 17 Jun 2026 02:50:33 +0000HIGH 7.5: An issue was discovered in Varnish Cache before 6.0.6 LTS, 6.1.x and 6.2.x before 6.2.3, and 6.3.x before 6.3.2. It occurs when communication with a TLS termination proxy uses PROXY version 2. There can be an assertion failure and daemon restart, which causes a performance loss.https://patchthecve.com/cve/CVE-2019-20637.htmlhttps://patchthecve.com/cve/CVE-2019-20637.htmlWed, 17 Jun 2026 02:30:51 +0000HIGH 7.5: An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6.3.1. It does not clear a pointer between the handling of one client request and the next request within the same connection. This sometimes causes information to be disclosed from the connecti