Varnish HTTP Cache

I’m new here, please explain this Varnish thing

What is happening

2021-03-16 - Denial of Service in varnish-modules

Some versions of the separate varnish-modules bundle allow for a potential denial of service attack when the header.append() or header.copy() functions are used.

Please see VSV00006 varnish-modules Denial of Service.

2021-03-15 - Varnish 6.6.0 is released

Our bi-annual”fresh” release is here: Varnish Cache 6.6.0

(The 2021-09-15 release is likely to be 7.0.0)

2020-11-06 - Varnish 6.0.7 is released

We are happy to announce the release of Varnish Cache 6.0.7.

This maintenance release is recommended for all users of the 6.0 LTS and contains several bug fixes, improvements and new features. More information is available in the Change log

2020-09-25 - Varnish 6.5.1 is released

When preparing the 6.5.0 release, it was forgotten to bump the VRT_MAJOR_VERSION number defined in the vrt.h include file. This major version bump is needed due to the API and ABI changes as part of the release, to make sure that VMODs are not allowed used if they were compiled for the wrong Varnish version.

This has been fixed in the Varnish Cache 6.5.1 release.

2020-09-15 - Varnish 6.5.0 is released

Come and get it… Varnish Cache 6.5.0

2020-03-16 - Varnish 6.4.0 is released

Our bi-annual “fresh” release Varnish Cache 6.4.0

2020-02-04 - Security Advisory: Denial of Service

All supported versions of Varnish suffer from a denial of service attack when using the Proxy Protocol version 2. Please see VSV00005.

2020-02-04 - Security releases: 6.0.6, 6.2.3 and 6.3.2

Varnish versions 6.0.6, 6.2.3 and 6.3.2 are now available. See VSV00005 for details.

Older news

Package repository status

The official Linux (apt/yum) package repositories are now located at A list of all available repositories can be found at:

For more details on packages, see Releases & Downloads


You can access the varnish-cache homepages with HTTP or HTTPS as you like.

We save the logfiles from our Varnish instance for a limited period, in order to be able to debug problems.

We do not use any external trackers and do not analyze traffic.