HashiCorp Vault 2.2 · Version Status

HashiCorp Vault 2.2 End of Life Date

HashiCorp Vault 2.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ HashiCorp Vault 2.2 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
2.2.1
Standard release
Release Date
Oct 14, 2026
HashiCorp Vault 2.2 series
Where these dates come from
ReleaseOct 14, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

HashiCorp Vault 2.2 was released on October 14, 2026 and has no published end-of-life date yet. It is not an LTS release; HashiCorp Vault reserves longer patch windows for its LTS versions. Its most recent patch is 2.2.1, published October 22, 2026.

← HashiCorp Vault 2.1 All HashiCorp Vault versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All HashiCorp Vault Versions
VersionLatestEOL DateStatus
1.9 1.9.10 Oct 10, 2022 EOL
1.10 1.10.11 Mar 1, 2023 EOL
1.11 1.11.12 Jun 21, 2023 EOL
1.12 1.12.11 Sep 27, 2023 EOL
1.13 1.13.13 Mar 25, 2024 EOL
1.14 1.14.10 Jun 10, 2024 EOL
1.15 1.15.6 Oct 8, 2024 EOL
1.16 LTS 1.16.3 Apr 30, 2026 EOL

What does HashiCorp Vault 2.2 end of life mean?

When HashiCorp Vault 2.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running HashiCorp Vault 2.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to HashiCorp Vault 2.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does HashiCorp Vault 2.2 reach end of life?
HashiCorp Vault 2.2 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is HashiCorp Vault 2.2 still supported?
Yes, HashiCorp Vault 2.2 is currently supported. The EOL date is TBD.
What should I upgrade to from HashiCorp Vault 2.2?
The recommended upgrade from HashiCorp Vault 2.2 is HashiCorp Vault 2.2 — the latest actively supported version. Check the HashiCorp Vault full timeline for all supported versions.
What are the security risks of running HashiCorp Vault 2.2 past EOL?
When HashiCorp Vault 2.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL HashiCorp Vault should migrate immediately or implement compensating controls.
Deep Dive
Version guide
HashiCorp Vault 1.20 End of Life: October 31, 2026
→
Data from endoflife.date API · Generated at build time · How we source data →