Skip to main content

Varnish Enterprise EUVDEUVD-2026-16801

| CVE-2026-34475 CRITICAL
Incorrect Behavior Order: Validate Before Canonicalize (CWE-180)
2026-03-27 cve@mitre.org
Critical
Disputed · 9.8 NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Leading special element handling
Impact

The CVSS 5.4 score (AV:N/AC:H/PR:N/UI:N/S:C) reflects network-reachable, unauthenticated attack surface with high complexity and partial impact (confidentiality and integrity, no availability loss). SSVC assessment categorizes this as low-urgency: exploitation status is 'none' (no confirmed active use), automatable status is 'no' (requiring manual crafting of specific URL patterns), and technical impact is 'partial' (not total system compromise). The CVSS AC:H (high complexity) qualifier significantly reduces real-world risk compared to simpler attack vectors. This is a genuine but limited-risk issue: cache poisoning and authentication bypass are serious in principle, but the high attack complexity and lack of automation or active exploitation suggest this is a lower-priority vulnerability relative to common Web application flaws. Organizations with strict cache integrity requirements or public-facing authentication systems proxied through Varnish should prioritize patching; others may defer based on patch availability and operational impact.

Exploit ScenarioDerived

An attacker sends an HTTP/1.1 request to a Varnish-proxied website with a crafted root-path URL (/) that is mishandled by the cache. Due to the unchecked req.url, Varnish caches the response with incorrect metadata or bypasses authentication checks. Subsequent requests from legitimate users receive the poisoned cached response, potentially exposing sensitive data or allowing attackers to inject malicious content. The attack requires moderate knowledge of the target application and Varnish configuration to succeed, explaining the high attack complexity rating. No public exploit code or active exploitation in the wild has been identified at the time of this analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
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 – Mar 27, 2026

Varnish Cache before 8.0.1 and Varnish Enterprise before 6.0.16r12 mishandle HTTP/1.1 URLs with a root path (/) in unchecked req.url scenarios, enabling cache poisoning and authentication bypass attacks. Unauthenticated remote attackers can exploit this with moderate complexity to poison cached content or bypass authentication controls affecting downstream clients. No active exploitation has been confirmed, though the vulnerability carries a 5.4 CVSS score reflecting network accessibility and partial impact to confidentiality and integrity.

RemediationAI

Upgrade Varnish Cache to version 8.0.1 or later, which includes the fix for improper HTTP/1.1 URL path handling. Varnish Enterprise users should update to 6.0.16r12 or later. For users unable to immediately patch, review and strengthen validation of req.url in Varnish Configuration Language (VCL) policies, ensuring that root path requests (/) are explicitly handled and do not bypass intended caching or authentication logic. Disable or restrict caching of authentication-sensitive responses until patched. Consult the official advisory at https://vinyl-cache.org/security/VSV00018.html for detailed configuration workarounds and patch deployment instructions.

Affected VersionsENISA

Varnish Cache 7.0.0 <8.0.1
Varnish Cache 0 <6.0.17 LTS

Affected Packages

euvd varnish_cache fix: 8.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 an HTTP accelerator and reverse proxy that caches web content to improve performance. The vulnerability stems from improper URL handling in HTTP/1.1 request processing, specifically when the path component is set to the root path (/). CWE-180 (Incorrect Behavior of Shift and Rotation Operator) typically involves bitwise operation errors, but in this context likely indicates unsafe transformation or normalization of URL path components. When req.url is not properly validated before use in caching decisions or authentication checks, attackers can craft malicious requests with root paths that bypass security controls. The affected versions are Varnish Cache before 8.0.1 (CPE: cpe:2.3:a:varnish:varnish_cache:*:*:*:*:*:*:*:*) and Varnish Enterprise before 6.0.16r12 (CPE: cpe:2.3:a:varnish:varnish_enterprise:*:*:*:*:*:*:*:*).

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

Sources disagree (Medium–Critical)
NVD PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SUSE 5.4 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Red Hat 5.4 MEDIUM

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorNVD

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

Lifecycle Timeline

4
Severity Changed
Oct 26, 2026 - 22:24 NVD
MEDIUM CRITICAL
CVSS changed
Oct 26, 2026 - 22:24 NVD
5.4 (MEDIUM) 9.8 (CRITICAL)
Patch available
Apr 16, 2026 - 05:29 EUVD
8.0.1,6.0.17
CVE Published
Mar 27, 2026 - 20:16 nvd
MEDIUM 5.4

DescriptionNVD

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.

Executive ViewAI

Why It Matters

CVE-2026-34475 presents moderate security risk rated CVSS 5.4. Exploitation could compromise the security of affected deployments. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor VulDB

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
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
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Low
Technical Impact
Partial

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

SUSE

Severity: Medium

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