Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2021-3169: An issue in Jumpserver before 2.6.2, before 2.5.4, before 2.4.5 allows attackers to create a connection token

61
This week
CRITICAL 9.8REMOTEUPGRADE

CVE-2021-3169 is a critical-severity flaw (CVSS 9.8) affecting jumpserver. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue in Jumpserver before 2.6.2, before 2.5.4, before 2.4.5 allows attackers to create a connection token through an API which does not have access control and use it to access sensitive assets.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.8% (top 14%)
CISA exploited listNo
WeaknessCWE-74
Published2021-07-23
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: jumpserver

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

jumpserver jumpserver UPGRADE
Affected: >= 2.4.0 and < 2.4.5 · >= 2.5.0 and < 2.5.4 · >= 2.6.0 and < 2.6.2
Fixed in: 2.4.5, 2.5.4, 2.6.2
Safe to downgrade to: a release before 2.4.0
1. Check installed version
apt-cache policy jumpserver || rpm -q jumpserver || jumpserver --version
2. UPGRADE to 2.4.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade jumpserver
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade jumpserver
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.4.0 (Debian / Ubuntu)
apt-cache madison jumpserver sudo apt install jumpserver=<VERSION_BEFORE_2.4.0> sudo apt-mark hold jumpserver
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list jumpserver sudo dnf downgrade jumpserver-<VERSION_BEFORE_2.4.0> sudo dnf versionlock add jumpserver
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-3169?

jumpserver: upgrade to 2.4.5, 2.5.4, 2.6.2. Exact commands for each OS are on this page.

Is CVE-2021-3169 being exploited?

CVE-2021-3169 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-3169 affect?

CVE-2021-3169 affects jumpserver. Severity is critical (CVSS 9.8). An issue in Jumpserver before 2.6.2, before 2.5.4, before 2.4.5 allows attackers to create a connection token through an API which does not have access control and use it to access sensitive assets.

How urgent is CVE-2021-3169?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.