Skip to main content

Varnish Cache EUVDEUVD-2026-21738

| CVE-2026-40394 HIGH
Always-Incorrect Control Flow Implementation (CWE-670)
2026-04-12 mitre GHSA-26pg-g54q-jv62
7.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Initiate HTTP/2 upgrade from HTTP/1
  2. Delivery
    Allocate buffer during transport switch
  3. Exploit
    Fragment workspace with prefetch data
  4. Execution
    Trigger pipelined fetch operation
  5. Persist
    Exhaust remaining workspace
  6. Impact
    Daemon panic and crash

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Always-incorrect control flow
Impact

The CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C) indicates network-based, unauthenticated attack with high complexity, affecting services across scope boundaries with only availability impact (daemon panic). EPSS of 4.0 reflects legitimate but bounded risk: attack vector is network-accessible (AV:N) and requires no privileges, but attack complexity is high (AC:H), requiring precise crafting of prefetch data amounts to trigger workspace exhaustion. The absence of public exploit code or CISA KEV confirmation suggests this remains theoretical or internally-managed by vendors. Real-world risk depends on whether attackers can reliably determine 'certain amounts of prefetched data' needed; if such tuning is difficult, practical exploitability remains low despite network accessibility. The scope change (S:C) indicates impact may extend beyond the vulnerable component, making this a moderate concern for CDN operators and reverse proxy deployments where Varnish absorbs traffic.

Exploit ScenarioDerived

An unauthenticated remote attacker sends a series of HTTP requests designed to trigger HTTP/1 to HTTP/2 upgrade with carefully calibrated prefetched data payloads. By timing and sizing the prefetch amounts to fragment the Varnish workspace and force subsequent pipelined fetch operations into workspace exhaustion, the attacker causes the daemon to panic and crash, temporarily disabling the reverse proxy and degrading service availability. The high attack complexity reflects the difficulty in determining exact payload sizes without intimate knowledge of workspace allocation internals.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAI

Denial of service via workspace overflow in Varnish Cache 9 before 9.0.1 and Varnish Enterprise before 6.0.16r11 allows unauthenticated remote attackers to trigger daemon panic through HTTP/2 session upgrade with specific amounts of prefetched data. The vulnerability exploits improper buffer allocation during HTTP/1 to HTTP/2 transport upgrade, causing workspace exhaustion on subsequent pipelined fetch operations. EPSS score of 4.0 (low-to-medium risk) reflects attack complexity and limited scope (local availability impact only), though no public exploit code or active exploitation has been confirmed.

RemediationAI

Upgrade Varnish Cache to version 9.0.1 or later, or upgrade Varnish Enterprise to version 6.0.16r11 or later. Administrators unable to patch immediately should monitor Varnish daemon logs for panic events triggered by workspace allocation failures during HTTP/2 session upgrade, and consider network-level rate limiting or request filtering on HTTP/2 upgrade attempts if feasible. Consult the vendor security advisory at https://docs.varnish-software.com/security/VEV00002/ for environment-specific guidance and confirmation of patched versions for your deployment.

Affected VersionsENISA

Varnish Cache 9.0.0 <9.0.1

Affected Packages

euvd varnish_cache fix: 9.0.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Varnish Cache is a high-performance HTTP accelerator and reverse proxy that manages request/response lifecycle using workspace buffers for memory allocation. The vulnerability resides in the HTTP/2 session initialization logic (CWE-670: Improper Error Handling) where a speculative HTTP/1 transport is established first, then upgraded to HTTP/2. During upgrade, the system allocates a buffer to reserve frame-sending capacity, which fragments the workspace. When the HTTP/1 request is repurposed as stream zero in the new HTTP/2 session and subsequent fetch operations attempt pipelining, the fragmented workspace becomes insufficient, causing allocation failure and daemon panic. The affected products are Varnish Cache versions prior to 9.0.1 and Varnish Enterprise versions before 6.0.16r11, as identified in the CPE string for a:varnish-software:varnish_cache.

Know when Varnish Cache gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Red Hat 5.9 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Severity Changed
Oct 26, 2026 - 21:23 NVD
MEDIUM HIGH
CVSS changed
Oct 26, 2026 - 21:23 NVD
4.0 (MEDIUM) 7.5 (HIGH)
Patch released
Apr 17, 2026 - 14:35 nvd
Patch available
Patch available
Apr 16, 2026 - 05:29 EUVD
9.0.1
CVE Published
Apr 12, 2026 - 19:17 nvd
MEDIUM 4.0

DescriptionNVD

Varnish Cache 9 before 9.0.1 and Varnish Enterprise before 6.0.16r11 allows a "workspace overflow" 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 repurposed as stream zero. During the upgrade, a buffer allocation is made to reserve space to send frames to the client. This allocation would split the original workspace, and depending on the amount of prefetched data, the next fetch could perform a pipelining operation that would run out of workspace.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2017-8807 CRITICAL
9.1 Nov 16

vbf_stp_error in bin/varnishd/cache/cache_fetch.c in Varnish HTTP Cache 4.1.x before 4.1.9 and 5.x before 5.2.1 allows r

CVE-2013-4484 MEDIUM POC
5.0 Nov 01

Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching out

CVE-2015-8852 HIGH
7.5 Apr 25

Varnish 3.x before 3.0.7, when used in certain stacked installations, allows remote attackers to inject arbitrary HTTP h

CVE-2017-12425 HIGH
7.5 Aug 04

An issue was discovered in Varnish HTTP Cache 4.0.1 through 4.0.4, 4.1.0 through 4.1.7, 5.0.0, and 5.1.0 through 5.1.2.

CVE-2026-40396 HIGH
7.5 Apr 12

Varnish Cache 9.0.0 crashes (denial of service) when a remote client exploits timing between timeout_linger and timeout_

CVE-2022-45060 HIGH
7.5 Nov 09

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 bef

CVE-2022-45059 HIGH
7.5 Nov 09

An issue was discovered in Varnish Cache 7.x before 7.1.2 and 7.2.x before 7.2.1. Rated high severity (CVSS 7.5), this v

CVE-2022-38150 HIGH
7.5 Aug 11

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

CVE-2021-28543 HIGH
7.5 Mar 16

Varnish varnish-modules before 0.17.1 allows remote attackers to cause a denial of service (daemon restart) in some conf

CVE-2020-11653 HIGH
7.5 Apr 08

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. Rated h

CVE-2019-15892 HIGH
7.5 Sep 03

An issue was discovered in Varnish Cache before 6.0.4 LTS, and 6.1.x and 6.2.x before 6.2.1. Rated high severity (CVSS 7

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy