CVE-2025-49825 — teleport
CRITICALCVE-2025-49825 is a critical-severity (CVSS 9.8) CWE-863 vulnerability in github.com/gravitational/teleport. A fix is available for github.com/gravitational/teleport — see the affected versions and patch details below.
Teleport allows remote authentication bypass
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-49825.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-49825 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/gravitational/teleport🐹github.com/gravitational/teleport🐹github.com/gravitational/teleport🐹github.com/gravitational/teleport🐹github.com/gravitational/teleport🐹github.com/gravitational/teleport🐹github.com/gravitational/teleportReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A full technical disclosure and open-source patch will be published after the embargo period, ending on June 30th, to allow all users to upgrade.
Teleport security engineers identified a critical security vulnerability that could allow remote authentication bypass of Teleport.
Teleport Cloud Infrastructure and CI/CD build, test, and release infrastructure aren’t affected.
For the full mitigation, upgrade both Proxy and Teleport agents. It is strongly recommend updating clients to the released patch versions as a precaution.
Have questions?
- OSS Community: [email protected]
- Legal: [email protected]
- Security: [email protected]
- Customer Support: goteleport.com/support
- Media Inquiries: [email protected]
Patches
Fixed in versions: 17.5.2, 16.5.12, 15.5.3, 14.4.1, 13.4.27, 12.4.35.
These patches are available only on the official Teleport distribution channels.
These versions are designated as Critical Security Exception Versions.
For these specific patch versions of Teleport Community Edition, the Community Edition restrictions are removed on employee count or revenue thresholds, as long as you apply the patch within thirty (30) days of its official release.
Please read the full text of the updated Teleport Community Edition license for details.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/gravitational/teleport | ≥ 17.0.0&&< 17.5.2 | 17.5.2go get github.com/gravitational/teleport@v17.5.2 |
| 🐹Go | github.com/gravitational/teleport | ≥ 16.0.0&&< 16.5.12 | 16.5.12go get github.com/gravitational/teleport@v16.5.12 |
| 🐹Go | github.com/gravitational/teleport | ≥ 15.0.0&&< 15.5.3 | 15.5.3go get github.com/gravitational/teleport@v15.5.3 |
| 🐹Go | github.com/gravitational/teleport | ≥ 14.0.0&&< 14.4.1 | 14.4.1go get github.com/gravitational/teleport@v14.4.1 |
| 🐹Go | github.com/gravitational/teleport | ≥ 13.0.0&&< 13.4.27 | 13.4.27go get github.com/gravitational/teleport@v13.4.27 |
| 🐹Go | github.com/gravitational/teleport | ≥ 0.0.11&&< 12.4.35 | 12.4.35go get github.com/gravitational/teleport@v12.4.35 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gravitational/teleport, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/gravitational/teleport to 17.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49825 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-49825 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-49825. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2025-49825
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-49825 -u https://target- Template
- Teleport - Authentication Bypass
- Severity
- critical
- Impact
- Attackers can bypass authentication mechanisms to gain unauthorized access to Teleport systems, potentially compromising protected infrastructure and sensitive resources.
- Remediation
- Upgrade Teleport to version 17.5.2, 16.5.12, 15.5.3, 14.4.1, 13.4.27, or 12.4.35 depending on your version branch.
Template by ProjectDiscovery nuclei-templates (pdteam), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-49825 in your dependencies?
O3 Security finds CVE-2025-49825 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.