EOL.Wiki EOL.Wiki
← ← Back to all products

Varnish

Active
Server Software Latest Version: 8.0.0 Latest Release: Sep 15, 2025

Varnish Cache is a high-performance HTTP accelerator designed for content-heavy dynamic websites.

Versions

10

Latest Version

8.0.0

Active Support

3

EOL

7

Lifecycle Timeline

Today
8.0
8.0
7.7
7.7
7.6
7.6
7.5
7.5
7.4
7.4
7.3
7.3
7.2
7.2
7.1
7.1
7.0
7.0
6.0
6.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
8.0Sep 15, 2025-Sep 15, 20268.0.0No
Active
7.7Mar 17, 2025-Mar 15, 20267.7.3No
Active
7.6Sep 13, 2024-Sep 15, 20257.6.5No
EOL
7.5Mar 18, 2024-Mar 15, 20257.5.0No
EOL
7.4Sep 15, 2023-Sep 15, 20247.4.3No
EOL
7.3Mar 15, 2023-Mar 15, 20247.3.2No
EOL
7.2Sep 15, 2022-Sep 15, 20237.2.1No
EOL
7.1Mar 15, 2022-Mar 15, 20237.1.2No
EOL
7.0Sep 15, 2021-Sep 15, 20227.0.3No
EOL
6.0Mar 15, 2018-No6.0.16
Yes
Active

Frequently Asked Questions

Which versions of Varnish have reached end of life?
The following Varnish versions have reached end of life and no longer receive security updates: 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Varnish 7.6?
Varnish 7.6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Varnish?
The latest version of Varnish is 8.0.0, released in the 8.0 release cycle.
How many versions of Varnish are currently supported?
Varnish currently has 3 actively supported version(s): 8.0, 7.7, 6.0.
When does Varnish 8.0 reach end of life?
Varnish 8.0 is scheduled to reach end of life on Sep 15, 2026.
What should I do when Varnish reaches end of life?
When a Varnish version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.