EOL.WikiEOL.Wiki
← ← Back to all products

OpenBao

Active
Security & NetworkingLatest Version: 2.5.5Latest Release: Jun 17, 2026

OpenBao is an open-source fork of HashiCorp Vault for secrets management and encryption.

Support summary

OpenBao currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

1

0 lts

Versions

6

Latest Version

2.5.5

Active Support

1

EOL

5

Lifecycle Timeline

Today
2.5
2.5
2.4
2.4
2.3
2.3
2.2
2.2
2.1
2.1
2.0
2.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.5Feb 5, 2026YesNo2.5.5No
Active
2.4Aug 28, 2025NoFeb 5, 20262.4.4No
EOL
2.3Jun 25, 2025NoAug 29, 20252.3.2No
EOL
2.2Mar 5, 2025NoJun 26, 20252.2.2No
EOL
2.1Nov 29, 2024NoMar 6, 20252.1.1No
EOL
2.0Jul 17, 2024NoNov 30, 20242.0.3No
EOL

Data sources

Frequently Asked Questions

Which versions of OpenBao have reached end of life?
The following OpenBao versions have reached end of life and no longer receive security updates: 2.4, 2.3, 2.2, 2.1, 2.0. It is recommended to upgrade to a supported version.
Is it safe to continue using OpenBao 2.4?
OpenBao 2.4 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 OpenBao?
The latest version of OpenBao is 2.5.5, released in the 2.5 release cycle.
How many versions of OpenBao are currently supported?
OpenBao currently has 1 actively supported version(s): 2.5.
When does OpenBao 2.5 reach end of life?
OpenBao 2.5 does not have a specific end-of-life date announced yet.
What should I do when OpenBao reaches end of life?
When a OpenBao 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.