EOL.WikiEOL.Wiki
← ← Back to all products

JumpServer

Active
Server SoftwareLatest Version: v4.10.16-ltsLatest Release: Mar 1, 2026

JumpServer is an open-source Privileged Access Management (PAM) bastion host that provides centralized, auditable access control to servers, databases, and devices.

Support summary

JumpServer 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

2

2 lts

Versions

3

Latest Version

v4.10.16-lts

Active Support

2

EOL

1

Lifecycle Timeline

Today
V4
V4
V3
V3
V2
V2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
V4Jul 15, 2024YesNov4.10.16-lts
Yes
Active
V3Feb 27, 2023YesNov3.10.21-lts
Yes
Active
V2Jun 1, 2020Dec 31, 2023Dec 31, 2025v2.28No
EOL

Data sources

Last verified

Jun 24, 2026

Community-maintained lifecycle data. Verify against official release notes before production migration.

Frequently Asked Questions

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