Skip to main content

Varnish Enterprise CVE-2026-40395

| EUVDEUVD-2026-21740 HIGH
Allocation of Resources Without Limits or Throttling (CWE-770)
2026-04-12 mitre
7.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Send HTTP request with excessive headers
  2. Delivery
    VCL invokes headerplus.write_req0()
  3. Exploit
    Workspace overflow in req0 buffer
  4. Execution
    Daemon panic and crash
  5. Impact
    Service becomes unavailable

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK

1 technique across 1 tactic: Impact

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L) indicates a network-accessible vulnerability requiring high attack complexity that affects availability across scope boundaries (causing daemon-wide impact from a request-level issue). The high attack complexity suggests an attacker must craft requests with a specific structure-excessive headers in the amended req-and this attack only succeeds when headerplus.write_req0() is actively used in the VCL configuration, limiting the practical attack surface. The low availability impact (A:L) reflects that this is a denial of service via crash, not data destruction. The lack of confirmed active exploitation (KEV status not indicated as active, no POC reported) and the requirement for VCL configuration that explicitly calls write_req0() reduce real-world priority for organizations not using Varnish Controller or headerplus module. However, for shared VCL deployments, this represents a straightforward, repeatable DoS vector that bypasses authentication (PR:N = no privileges required) and thus merits timely patching despite the moderate CVSS score. The SSVC decision framework would classify this as: Exploitation=Unkown (no POC/KEV), Automatable=Yes (header-based attack requires no user interaction), Technical Impact=Total (daemon crash), pushing toward at least coordinated patching rather than differed remediation.

Exploit ScenarioDerived

A malicious client sends a series of HTTP requests with a large number of header fields (e.g., hundreds of custom headers or duplicated standard headers) to a Varnish Enterprise instance running shared VCL with the Varnish Controller and vmod_headerplus module active. When the VCL processes the request via write_req0(), the function attempts to write the amended request object-now containing excessive headers-back to the read-only req0 workspace. The workspace allocation is insufficient to hold the expanded header set, triggering a buffer overflow and immediate daemon panic. The Varnish server crashes, causing a complete denial of service until manual restart.

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

AnalysisAIv1 – Apr 12, 2026

Varnish Enterprise before version 6.0.16r12 is vulnerable to a workspace overflow denial of service attack that crashes the daemon through the headerplus.write_req0() VCL function. Unauthenticated remote attackers can craft HTTP requests with excessive header fields to trigger a panic and terminate the Varnish server, particularly impacting deployments using shared VCL through Varnish Controller. CVSS base score of 4.0 reflects low availability impact with high attack complexity, and no public exploit code or confirmed active exploitation has been identified.

RemediationAI

Upgrade Varnish Enterprise to version 6.0.16r12 or later. This release includes fixes to the headerplus.write_req0() function to properly validate header field counts and workspace capacity before writing amended request headers back to req0, preventing the workspace overflow condition. As a temporary workaround for organizations unable to upgrade immediately, review and restrict VCL configurations that invoke headerplus.write_req0(), ensuring that incoming requests are validated or rate-limited to prevent excessive header field injection attacks. Consult the Varnish Software security advisory at https://docs.varnish-software.com/security/VEV00003/ for detailed patching procedures and configuration guidance specific to your deployment.

Affected VersionsENISA

Varnish Enterprise 6.0.9r5 <6.0.16r12

Affected Packages

euvd varnish_enterprise fix: 6.0.16r12

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 Enterprise is a reverse proxy and HTTP accelerator that uses VCL (Varnish Configuration Language) for request processing. The vmod_headerplus module provides the write_req0() function to update the underlying req0 object (the original read-only request from which the writable req object is derived in VCL). This capability is essential for shared VCL deployments orchestrated by Varnish Controller, where requests are refined in one VCL context before switching to another via vcl(<label>) return statements. The vulnerability stems from insufficient bounds checking when writing amended request headers back to req0's workspace allocation. When the amended req object contains more header fields than req0's workspace can accommodate, a buffer overflow occurs in the workspace memory region, triggering a daemon panic. The root cause is classified as CWE-770 (Allocation of Resources Without Limits or Throttling), indicating the function lacks proper validation of header field count or size before attempting the write operation.

Know when Varnish Enterprise 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 4.0 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 - 22:24 NVD
MEDIUM HIGH
CVSS changed
Oct 26, 2026 - 22:24 NVD
4.0 (MEDIUM) 7.5 (HIGH)
Patch released
Apr 17, 2026 - 14:37 nvd
Patch available
Patch available
Apr 16, 2026 - 05:29 EUVD
6.0.16r12
CVE Published
Apr 12, 2026 - 19:21 nvd
MEDIUM 4.0

DescriptionNVD

Varnish Enterprise before 6.0.16r12 allows a "workspace overflow" 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 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.

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.

Vendor StatusVendor

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