Synced 16 Jun 2026 15:24 UTC Account
← Teleport

Teleport vulnerabilities: known CVEs & security history

Gravitational · Security / Access · 5 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Teleport release lines — 5 in total. A CVE here doesn't mean your version is affected — check Teleport's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known Teleport CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2021-41393 critical 9.8 1% 2021
CVE-2022-36633 high 8.8 49% 2022
CVE-2022-38599 medium 6.5 1% 2022
CVE-2021-41395 medium 6.5 1% 2021
CVE-2021-41394 medium 5.3 1% 2021

Is my Teleport version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Teleport version → · Monitor Teleport for new CVEs →

Teleport vulnerabilities — frequently asked

How many known vulnerabilities does Teleport have?

IsItPatched tracks 5 CVEs for Teleport. 1 is critical-severity and 1 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Teleport have any actively-exploited vulnerabilities?

None of Teleport's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Teleport vulnerability?

Among tracked issues, CVE-2021-41393 (CRITICAL, CVSS 9.8) ranks highest.

Is Teleport safe to use?

It depends on the version. The latest supported Teleport release (18.8.3) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Teleport security status · Teleport end-of-life · actively-exploited CVEs. Always verify against Gravitational's advisories — see our disclaimer.