cve.bz

CVE-2026-34475

9.8 criticalEPSS 0.2%

Critical (9.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-180 Incorrect Behavior Order: Validate Before Canonicalize
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34475 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34475?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34475?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34475 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
varnish-software Varnish Cachebefore 6.0.17 LTS
varnish-software Varnish Cachefrom 7.0.0 before 8.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12varnishno fix listedDEBIAN-CVE-2026-34475
Debian13varnish7.7.0-3+deb13u2DEBIAN-CVE-2026-34475 DSA-6584-1
Ubuntu14.04:LTS, 24.04:LTS, 25.10 and 6 morevarnishno fix listedUBUNTU-CVE-2026-34475

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10redhat-user-workloads/varnish-7-10-0Not affected
Red Hat Enterprise Linux 10redhat-user-workloads/varnish-7-10-1Not affected
Red Hat Enterprise Linux 10varnishFix deferred
Red Hat Enterprise Linux 10varnish-modulesFix deferred
Red Hat Enterprise Linux 8redhat-user-workloads/varnish-6-8-10Not affected
Red Hat Enterprise Linux 8varnish:6/varnishFix deferred
Red Hat Enterprise Linux 8varnish:6/varnish-modulesFix deferred
Red Hat Enterprise Linux 9redhat-user-workloads/varnish-6-9-6Not affected
Red Hat Enterprise Linux 9redhat-user-workloads/varnish-6-9-7Not affected
Red Hat Enterprise Linux 9varnishNot affected
Red Hat Enterprise Linux 9varnish-modulesFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-34475.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON