CVE-2022-45060: 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

This month

HIGH 7.5REMOTEWATCHLISTUPGRADEDOWNGRADEUPGRADE

CVE-2022-45060 is a high-severity flaw (CVSS 7.5) affecting varnish cache, varnish cache plus, varnish cache. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 invalid HTTP/1 requests to the backend. This could, in turn, be used to exploit vulnerabilities in a server behind the Varnish server. Note: the 6.0.x LTS

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Weakness	CWE-20
Published	2022-11-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: debian · fedoraproject · varnish cache project · varnish-software

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-11-09 06:15 UTCPublished CVE record published
2026-06-17 05:09 UTCUpdated Record last modified

varnish-software varnish cache UPGRADE

Affected: >= 6.0.0 and < 6.0.11

Fixed in: 6.0.11

Safe to downgrade to: a release before 6.0.0

1. Check installed version

apt-cache policy varnish-cache || rpm -q varnish-cache || varnish-cache --version

2. UPGRADE to 6.0.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade varnish-cache

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade varnish-cache

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)

apt-cache madison varnish-cache sudo apt install varnish-cache=<VERSION_BEFORE_6.0.0> sudo apt-mark hold varnish-cache

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list varnish-cache sudo dnf downgrade varnish-cache-<VERSION_BEFORE_6.0.0> sudo dnf versionlock add varnish-cache

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

varnish-software varnish cache plus DOWNGRADE

Affected: 6.0.0 · 6.0.0 r0 · 6.0.0 r1 · 6.0.0 r2 · 6.0.1 r1 · 6.0.1 r2 · 6.0.1 r3 · 6.0.1 r4

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.0.0

1. Check installed version

apt-cache policy varnish-cache-plus || rpm -q varnish-cache-plus || varnish-cache-plus --version

2. No fixed release: DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)

apt-cache madison varnish-cache-plus sudo apt install varnish-cache-plus=<VERSION_BEFORE_6.0.0> sudo apt-mark hold varnish-cache-plus

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list varnish-cache-plus sudo dnf downgrade varnish-cache-plus-<VERSION_BEFORE_6.0.0> sudo dnf versionlock add varnish-cache-plus

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

varnish cache project varnish cache UPGRADE

Affected: >= 5.0.0 and < 6.0.11 · >= 7.0.0 and < 7.1.2 · 7.2.0

Fixed in: 6.0.11, 7.1.2

Safe to downgrade to: a release before 5.0.0

1. Check installed version

apt-cache policy varnish-cache || rpm -q varnish-cache || varnish-cache --version

2. UPGRADE to 6.0.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade varnish-cache

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade varnish-cache

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)

apt-cache madison varnish-cache sudo apt install varnish-cache=<VERSION_BEFORE_5.0.0> sudo apt-mark hold varnish-cache

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list varnish-cache sudo dnf downgrade varnish-cache-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add varnish-cache

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

fedoraproject fedora MITIGATE

Affected: 35 · 36 · 37

Fixed in: no fixed release known

Safe to downgrade to: a release before 35

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

debian debian linux MITIGATE

Affected: 10.0 · 11.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 10.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-45060?

varnish cache: upgrade to 6.0.11; varnish cache plus: downgrade or apply the listed mitigation; varnish cache: upgrade to 6.0.11, 7.1.2. Exact commands for each OS are on this page.

Is CVE-2022-45060 being exploited?

CVE-2022-45060 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-45060 affect?

CVE-2022-45060 affects varnish cache, varnish cache plus, varnish cache. Severity is high (CVSS 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

How urgent is CVE-2022-45060?

Priority 52/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Debian vulnerabilities · Varnish vulnerabilities

Related CVEs

CVE-2022-45059 HIGH 7.5 UPGRADE MITIGATE An issue was discovered in Varnish Cache 7.x before 7.1.2 and 7.2.x before 7.2.1
CVE-2022-38150 HIGH 7.5 DOWNGRADE MITIGATE 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 auto
CVE-2022-23959 CRITICAL 9.1 UPGRADE UPGRADE 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 Enter
CVE-2021-36740 MEDIUM 6.5 UPGRADE UPGRADE Varnish Cache, with HTTP/2 enabled, allows request smuggling and VCL authorization bypass via a large Content-

References

← Back to latest CVEs